Hi Rick,
Rick Bullotta wrote:
You answered the key question - how to suppress mutation events and other such things. We load SVG, manipulate it, then render it. We wanted to avoid any extraneous processing relative to events, and from your post, it seems that it would happen "auto-magically" for us when using the transcoders.
So this is mostly true. The mutation events will still be fired but no one will be listening. This should represent a very small amount of additional overhead. If even this is a problem this part is fairly easy to stop since all the event dispatching goes through batik.dom.event.EventSupport.dispatchEvent.
But I don't think dispatching the events should be a big deal as long as no one is listening.
Many thanks, and happy new year!
- Rick
---- Thomas DeWeese <[EMAIL PROTECTED]> wrote:
Rick Bullotta wrote:
Is there any easy way to build Batik without of the scripting infrastructure (for use in server-side applications). We manually stripped out all of the scripting code, but that is obviously not a desirable approach long term.
Why do you care about the size for server-side applications? If you don't want any of the 'dynamic' features enabled simply tell the BridgeContext to be STATIC (this is the default for the Transcoders).
What scripting code are you stripping out?
--------------------------------------------------------------------- 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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
