--- Finn Bock <[EMAIL PROTECTED]> wrote:
> > I.e., for all those references to the 'foo'
> property
> > instance for the children of an FO where that
> value
> > would be inherited, we don't have to create a new
> > Property instance, just a reference to the
> inherited
> > instance.
> Right, that is also the way I see it.

Good, all three of us are on the same page.

> 2) Put the relevant properties in a fast Property[]
> array and the
>     remaining specified properties in a HashMap. For
> fo:root the result
>     would be an array of size 1 for the
> 'media-usage' property.

No, I wasn't thinking of having a HashMap at all--just
a property array--first populated by incoming
specified properties, then populated by querying the
PropertyWindow for ancestor already-created property

The PropertyWindow is only a FO-tree build time
convenience for quickly attaching already created
property instances to the current node, without
needing to make recursive calls up the tree to obtain
those instances.  It is not needed if (1) the
recursion is not that big a deal in time, or (2) it is
not desired to store an array of all valid instances
for each FObj (i.e., we should continue something
similar to what HEAD does presently).  

However, its usage may also eliminate the need to
store all relevant properties for the children in the
array of each FObj.  (i.e., fo:root can return to just
storing media-usage.)  Of course, it is certainly more
space-efficient to store 250 properties at the top
than at each of the child nodes.  Ultimately, it
depends on what you want the property arrays for each
FObj instance to store.


Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes

Reply via email to