Re: [office-collab] Let's Keep the Cases Straight

[monkeyiq <monkeyiq@gmail.com>]

Hi,
  On page 17 of the extended proposal the example shows the entire
draw:frame replaced for any change. On the other hand, reading the GCT
proposal as it stands one would implement atomic changes such as 6.3.2
for style modifications to a caption: 
<text:span delta:insertion-type='insert-around-content' ...>

  So the view in this particular example is founded on the proposals
themselves. Stepping back from the ECT/GCT comparison, I think the
larger trap is to force context dependant processing on common elements
such as text:p.

  In abiword, and I'd imagine in many other applications, the load path
for ODF uses the same code to turn text:p elements and their children
into the internal objects that the application uses to represent the
document. Frank Meies has commented that OOo uses this same scheme where
all text:p use the same codepath. 

  The context dependant processing of text:p means that such code paths
would have to be duplicated; one for text:p elements at top level, and
another for text:p elements buried inside a bucket.


On Sun, 2011-04-24 at 14:34 -0700, Dennis E. Hamilton wrote:
> I notice that there is a tendency to view whatever already happens
> using the ODF 1.x change tracking as part of ECT and that GCT escapes
> it.
...
> -----Original Message-----
> From: monkeyiq [mailto:monkeyiq@gmail.com] 
> Sent: Sunday, April 24, 2011 01:30
> To: Frank Meies
> Cc: office-collab@lists.oasis-open.org
> Subject: Re: [office-collab] Suggestions for moving forward to resolve issues
> 
> On Fri, 2011-04-22 at 12:55 +0200, Frank Meies wrote:
> > That's what OOo currently does. There is no difference (neither in the 
> > generated xml nor in the internal structures) if you change the 
> > caption text:p or any other paragraph in the document.
> 
> So in this particular case, the ECT as it stands is actually a fair bit harder to implement than the GCT. The ECT requiring two very different IO paths depending on context.
> 
> [ ... ] 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 
>