I hate when people post questions, find their own solution, and then 
never answer their own question for the sake of future poor souls, 
so I'm following up on what I've found.

A major issue with our performance was related to the use of 
the "visibility" attribute (specifically "hidden") compared to using 
the "display" attribute (set to "none").

For a given location in our displays, this location may show any one 
of a number of different images that represent the current state of 
something, let's say, the current state of the moon (waxing, waning, 
quarter, half, full, etc).

As the SVG files are currently setup, the images that are not 
visible (not reflecting the current state) are "hidden" via 
visibility="hidden".  When I modified the SVG to use display="none" 
the displays were able to be called up **4 time faster**.  Checking 
the SVG spec 
(http://www.w3.org/TR/SVG11/painting.html#VisibilityControl)
indicates why.  From the spec:

"When the 'display' property is set to none, then the given element 
does not become part of the rendering tree."

So, you can see that Batik can handle the GVT build and render much 
more easily because it can "ignore" the items that are set to 
display="none".  In the old way, visibility="hidden" still results 
in the non-current images being rendered.

Thanks to everyone for your help.  I'm sure that you all would have 
pointed this out immediately if I would have been able to post a 
file, but I did not have the liberty to do so.






-----
To unsubscribe send a message to: [EMAIL PROTECTED]
-or-
visit http://groups.yahoo.com/group/svg-developers and click "edit my 
membership"
---- 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/svg-developers/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 



Reply via email to