2009/1/13 Tom Morris <[email protected]>: > I'm sure Batik would improve the quality of the SVG generation, but I > don't think it's necessary to get GEF to implement Graphics2D. The > current SVGWriter implements only the portion of the Graphics > interface which is used by GEF and having implementing the same > fraction of the Graphics2D interface doesn't really look like it would > be a lot of work, particularly since the SVG drawing model seems to > support pretty much everything that's needed in a fairly direct > fashion.
If someone can help in improving GEFs SvgWriter that is fine. Help is always welcome in GEF. > > On Mon, Jan 12, 2009 at 8:17 PM, Bob Tarling <[email protected]> wrote: > >> 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 > > Adding a megabyte of stuff to get a single class seems pretty > heavyweight. If you did decide to use Batik, how much of this is > really necessary? BATIK actually comes larger than this, it's packaged with SVG viewers etc but I cut those out. This is actually the minimum required. It's possible that batik may provide some further graphics formats for us but I'd like to start with SVG alone. BATIK can generate, JPEG, PNG or TIFF, EPS or PDF. Some of those we can generate ourselves by other means but we can at least compare performance and memory consumption.
