Hi, On Feb 5, 2008 10:51 PM, Luca Piccarreta <[EMAIL PROTECTED]> wrote: > Hi Tom, > I'm developing an SVG editor. And... I can't imagine many scenarios in which > bidirectional interaction is so frequent with the SVG document. > The best solution I found was an MVC approach, in which the document is > a simple Apache DOM document, the view is a Batik Document, and the > controller is a hierarchy of objects that forward DOM Mutation Events to > the Batik Document.
Same here, We also developing SVG Editor and using similar pattern like yours (MVC pattern). In our case: - Model -> SVGDocument wrapped in model class - View -> our VectorCanvas - Controller -> embedded in both the Model and VectorCanvas Note: VectorCanvas is not descendant of JSVGCanvas or JSVGComponent. Cheers Tonny Kohar -- Sketsa SVG Editor imagine, design, create ... http://www.kiyut.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
