Olli Tietäväinen (![[info]](http://l-stat.livejournal.com/img/userinfo.gif){kind=small} ottietav) wrote,@ 2006-12-12 10:37:00 |
|
XML woes
I'm currently working with SVG files, which (in case you didn't know) are vector graphics stored in XML form. SVG is a pretty nifty thing, since it allows quite small files (depending on the complexity of your image), lossless image quality and automated image processing. The last item is what's currently bugging me, mainly because some simple things are just too hard. In an ideal world, I'd just need to do something like this to edit some SVG:
Unfortunately, in actuality (Java) I also need things like a resource descriptor, a document factory, a svg generator context, a svg generator, a file output stream, a buffered output stream, a stream writer and other things I haven't yet discovered. I find myself copy/pasting lots of code just because. This Is Not The Right Way.
EDIT: I can't really be mad when I'm using a Transformer Factory.
I'm currently working with SVG files, which (in case you didn't know) are vector graphics stored in XML form. SVG is a pretty nifty thing, since it allows quite small files (depending on the complexity of your image), lossless image quality and automated image processing. The last item is what's currently bugging me, mainly because some simple things are just too hard. In an ideal world, I'd just need to do something like this to edit some SVG:
SVGDocument doc = SVGDocument.parse(filename); noodleXml(doc); // do something doc.saveToFile(filename);
Unfortunately, in actuality (Java) I also need things like a resource descriptor, a document factory, a svg generator context, a svg generator, a file output stream, a buffered output stream, a stream writer and other things I haven't yet discovered. I find myself copy/pasting lots of code just because. This Is Not The Right Way.
EDIT: I can't really be mad when I'm using a Transformer Factory.
