Hi Peter,
Peter Wagener <[EMAIL PROTECTED]> wrote on 03/02/2006 09:17:31
AM:
> This works, but I'm a little worried about performance. The
> documents themselves are on the large side: the chassis is ~2MB, the
> sub-documents are between 200KB and 1MB. It's possible that a
> chassis may have up to 20 - 30 components on the high side.
Why so large? Given the stated purpose I would have expected
the rack to be a fairly simple. Similarly for the sub documents.
> Also, a more recent test of this technique was throwing
> BridgeException's at seemingly random times on one of the
> many the 'appendChild' calls.
What sort of bridge exception? Out of Memory?
> Is there a better way to accomplish this? I've looked into using
> Overlay's, but am struggling with how I would draw an SVG from the
> Overlay's 'paint(...)' method.
Well you might be able to call the 'paint' method on the root of
a GVT tree. But I'm not sure what you are hoping to save here?
> I've also thought of rasterizing the SVG of each component, and
> drawing that way from within an Overlay, but would I then lose
> the ability to zoom in & out?
You could render the component to a BufferedImage at the start
of the 'drag' operation and then just draw that. You might need to
be careful that your BufferedImage didn't get too large.
> Any code snippets I could look at that do similar things?
I would look at simplifying the graphics I have a hard
time understanding why these elements would need to be so
detailed...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
