Hi Rene, scr <[EMAIL PROTECTED]> wrote on 04/30/2007 09:06:23 AM:
> My problem now is just the loading of the files (~7s for about 14.000 > elements), that is the time from opening to the first time user can see the > content. Do you know what the basic breakdown of time is? Parsing XML, Building GVT tree, Rendering Prep, actual rendering? The Batik Squiggle Browser can print this out to the console if you turn on, Edit->Preferences->General->Print debugging information to console. > Our goal is to reduce the time < 2s - I'm sure there is a way ;) > Rendering seems not be a large problem, since elements (static and dynamic) > are not very complicated. > > Is there a possibility to persist the processed GVT and/or DOM as Java > Objects to disk and reload it next time? Has anyone tried yet? Well the best way to persist DOM to disk is as XML ;) The problem with GVT is that it has some ugly bindings to things like Fonts that make it complicated to serialize them. > Is there an alternative to this idea (support by batik API)? Or are there > other possibilities to increase performance loading such wired SVG files > which I may have overseen, yet? What would a wired SVG file be? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
