Thorbjørn Ravn Andersen wrote:
I have now made a comparison between 0.20.5 and the latest maintainance code in CVS, and I do not see the effects described above. I have tested with the sample AWT-previewer in FOP, and found that the memory footprint are very similar, but I will now check in the actual environment. Do I need to provide some configuration parameters which may change the behaviour of FOP?
The changes to Table performance dont apply to AWT Renderer mainly because AWT Rendering uses very different code to the main part of FOP's layout/rendering engine, which is geared up for PDF, Postscript and other print formats.
<snip/>
By accident I first checked with the code in HEAD, which did not work well, so I am convinced that 1.0 is still some time away :)
Could you elaborate on what isnt working? One of my current goals is to get the development version working to a similar level as 0.20.5.
Chris
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
