Hi, > We've been using Batik to create interactive visualization tools > in Java. One issue we have is about Batik's memory footprint > and that is may not scale. Specifically, the scenario we are worried > about is when there are a large number of svg canvases (50-100) open > each displaying a set of visual objects. Although, only one or two > canvases need to be visible at a given time, the users need to be able > to quickly switch among the canvases. Clearly, we have to be smart > about memory management. So, first, I would like to know if there is > any recommendation for how to optimize memory usage for batik > in general. In addition, I would like to know if there is any way > to quickly free up memory for a canvas that has become hidden > and be able to quickly switch back to it.
According to SVG Spec, you could set the display attribute to none, but I am not sure whether Batik adhere to this particular spec attribute or not. From my test, it Batik comply with the spec, but to be sure maybe Thomas know the answer? Best Regards Tonny Kohar -- Sketsa SVG Graphics Editor http://www.kiyut.com ----- 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/
