Salut Renaud I wondered about that, too: http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&by=thread&from=984481
So far, I can only say that there's so mandatory reason for that change. It would certainly make the renderers simpler but there might be problems in other areas. The real downside is when you have to do the same calculations in every renderer. Some can be (and already are) put in AbstractRenderer but for others this is not so easily possible. No definitive answer from me. We'll see what comes out of the page-break rewrite. On 22.02.2005 20:28:56 Renaud Richardet wrote: > bonjour fop-dev's > > i've been walking through the rendering process. if i understand it > rightly, an area doesn't records it's absolute position. therefore, we > have to pass the currentIPPosition, currentBPPosition all along during > the rendering process to figure out where to position an area. > what i don't understand: this information (the absolute position of an > area) MUST somehow have been known during the building of the area > tree (otherwise we could'nt know where to break the pages). so my > question: wouldn't it be easier to record the absolute position of an > area during the page-breaking process? or am i missing something? > > renaud > > PS: the abstract Java2DRenderer sounds like a really good deal to me :) Jeremias Maerki
