Hi George,

Another alternative which I haven't tried yet is to simply replace the
whole JSVGComponent in the frame with one that already has the doc
loaded.  But that seems like overkill.  Any other ideas for a speedup?

This is exactly what I would do. I'm not sure why you consider this overkill. If you do this properly you can even have it prerendered to it's offscreen buffer providing essentially instantaneous transition. Somewhere way down on my list of things todo is to rewrite the slideshow app so it does this.

I have not done any detailed profiling, but from cursory "println"
testing most of the time seems to be spent in the GVTTreeBuild phase.

This would be the text. We've spend a lot of time on it but text is still 10x slower than I would like to see it.

Which leads me to my question- is there a recommended way to specify a
pre-built GVT Tree to the JSVGComponent when changing SVGDocuments?
I'm thinking of designing something along the lines of a

  setSVGDocument(SVGDocument doc, GraphicsNode gvtRoot)

Such an API would allow me to pre-build the next document and tree for
display, assuming I can correcly anticipate the user's next move.

The problem is that you would also need to provide at least the BridgeContext, UpdateManager, user agent(?_ and probably a few other
things I'm not thinking of for this to work. It's so complex
that the chances of the hand off being successful without being
intimately aware of the internals of the JSVGCanvas (i.e. subclassing)
are very low.


   If the documents are static you could potentially judy
use the JGVTComponent.

George Armhold wrote:

I'm trying to improve the loading/rendering time of the JSVGComponent
for handling multiple successive SVGDocuments.  The app allows the
user to step through a series of documents in response to a keypress.
For some documents (typically ones with lots of text) the
setSVGDocument() call can be very slow, on the order of 2-3 seconds.
That may not sound like much, but when you're in "browsing mode" it
can be painful for the user.  Note that I am already pre-constructing
the documents via SAXSVGDocumentFactory.createDocument().



Thanks.


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to