Hi Bob, This sounds good. I would be nice though if it was simply a utility method call. This would allow us to use it not only in the graphics exporter but also in ArgoPrint. The DiagramUtil#getDiagramAsSVG shows our current usecase.
http://argoprint.tigris.org/source/browse/argoprint/trunk/src/org/argoprint/util/DiagramUtil.java?revision=327&view=markup This method call is typically embedded within a template. This allows template developers to embed SVG images in an XML-based document. Mark On Mon, Jan 12, 2009 at 5:17 PM, Bob Tarling <[email protected]> wrote: > I've done some experiments in one of the GEF demo apps using batik to > generate SVG rather than using GEFs own implementation. > > One of the main difference is that batiks version extends Graphics2D > whereas GEF extends Graphics. The fact that GEF has such an old type > of Graphics implementation is hindering further improvements to the > java2d code in its paint methods, > > I'd like to try implementing this in ArgoUML and drop use of the GEF > version. If this proves successful then GEF can drop this facility > expecting batik to be used instead. > > I'm considering trying to implement this as a module can register > itself in ArgoUML as a graphics exporter. > > Now is not a good time with the releases approaching and the issues I > need to deal with but I just wanted to make mention of this to check > if the concept sounds ok. > > From batik we need the following jars (939Kb) > > batik-awt-util.jar > batik-dom.jar > batik-ext.jar > batik-svggen.jar > batik-util.jar > batik-xml.jar > > Usage of batiks SVGGraphics2D is described here - > http://xmlgraphics.apache.org/batik/using/svg-generator.html > > It is the Apache licence version 2 - > http://www.apache.org/licenses/LICENSE-2.0 > > Regards > > Bob > >
