On Mon, Feb 16, 2004 at 08:22:31PM +0100, Andreas L. Delmelle wrote: > > -----Original Message----- > > From: Finn Bock [mailto:[EMAIL PROTECTED] > > > > [Simon Pepping] > > > <snip /> > > > However, I am not happy with your > > > solution. During the layout process, you feed the page dimensions back > > > into the FO tree, in PageLayoutManager.createPageAreas. > > > > Yes, and in BlockLayoutManager and in all the other LM that defines base > > length for percentages. > > > > > I think it > > > would be a better design if, in order to resolve the percent-based > > > properties, you would not climb the FO tree but the Area tree. That > > > avoids feeding back results from the Area tree into the FO tree. > > > > > Yes, but... isn't it the main idea that we serialize the FO tree for > possible later re-use? Independently of the Area tree? > > In that case, it seems more than logical to feed these back into the FOT > once, instead of re-resolving them from the AT when the document is rendered > anew?
If in the re-use the layout would not change, the area tree could be reused. OTOH, if the layout would change, e.g. because another renderer would use a font with a different font metric, the layout information in the FO tree cannot be reused. This is another argument to separate FO tree and layout information. Regards, Simon Pepping -- Simon Pepping home page: http://www.leverkruid.nl