At 05:41 PM 7/15/01 +1000, Mark wrote:
> I hope noone is offended by my work/writing on this stuff, I realise that
>FOP is experimental but the number of changes are surprisingly small and
>the results are just so cool. Memory use is significantly reduced for all
>cases where there is more than one page-sequence, and total time to render
>seems to be significantly reduced. If anyone is interested in a summary of
>the changes I made then drop me a line.
I'm personally only offended by being referred to as a "fopsicle". Just
kidding. :-)
Seriously, this is great stuff. You should be aware that the initial memory
buffering that you see with the -buf switch is only a limited portion of
more extensive work that has yet to be folded into FOP. This latter is an
extensive patch, and I have not had the time to commit it (well, there have
been a few other glitches). The developer that has been doing that is now a
committer, and I hope that the rest of the memory buffering code will soon
appear in CVS. Nevertheless, it seems to me like you are doing complementary
things, a diferent approach, and perhaps we will be able to finally see
elements of both approaches working together.
This is open-source; nobody should be offended by people hacking away at code.
Specific comments; IDReferences have mostly to do with
<fo:page-number-citation/>, that is, the possibility is there that you need
the page number that contains the results of rendering the block with
id="foo356", and you're currently on page 44, and the block with id="foo356"
will end up on page 887, although you don't know that yet. You're right,
this kind of stuff can cause major issues for pipelining. Nothing
insurmountable, though.
The code you see in Root.java should not require page-sequence N+1 to be
formatted before you render page-sequence N. All that's going on there is,
if the "force-page-count" property on page-sequence N is "auto", it needs to
know about the "initial-page-number" property on page-sequence N+1. This
doesn't require any formatting to take place at all.
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
