Apache Wiki
Sat, 10 May 2008 06:57:38 -0700
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Xmlgraphics-fop Wiki" for change notification. The following page has been changed by AndreasDelmelle: http://wiki.apache.org/xmlgraphics-fop/PropertyHandling/PropertyCache ------------------------------------------------------------------------------ So, 124.017 objects will live in the Java heap, until the table is fully rendered, and this still excludes any further content or any layout-related classes. - Before the introduction of the {{{PropertyCache}}}, if the author were to specify an explicit font-size of "10pt" on all the {{{fo:table-cell}}}s, this would lead to an equal amount of distinct {{{FixedLength}}} instances. This could be avoided by making use of property inheritance: specify the property on the ancestor {{{fo:table}}}, and through inheritance, only one {{{FixedLength}}} instance was needed for the entire table, as the same instance would be picked up by the {{{PropertyList}}}s responsible for resolving the cells' properties. Ultimately, this could be brought down to one instance for the whole document, by specifying the global font-size on the {{{fo:root}}}. + Before the introduction of the {{{PropertyCache}}}, if the author were to specify an explicit font-size of "10pt" on all the {{{fo:table-cell}}}s, this would lead to an equal amount of distinct {{{FixedLength}}} instances. This could be avoided by making use of property inheritance: specify the property on the ancestor {{{fo:table}}}, and through inheritance, only one {{{FixedLength}}} instance was needed for the entire table, as the same instance would be picked up by the {{{PropertyList}}}s responsible for resolving the cells' properties. Ultimately, this could be brought down to one instance for the whole document, by specifying the global font-size on the {{{fo:root}}}. After the introduction of the {{{PropertyCache}}}, using inheritance still has its benefits. Even if the memory consumption would be roughly the same, inheritance eliminates the need to parse the properties at all for the descendants. Note: a fact overlooked by many is that, according to the XSL-FO Recommendation, '''any''' property may be specified on '''any''' formatting object. The fact that the font-size property does not apply to {{{fo:root}}} still does not mean that the property will be entirely lost. Due to regular inheritance, '''all''' {{{PropertyList}}}s will ultimately use the value of the root {{{PropertyList}}} unless an override is provided on a deeper level. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]