Should I rather start with the "root" field from SVGAbstractTranscoder after its transcode() method? It seems to do all the necessary preparations.
The problem is that the 'root' field is the GVT tree. The existing code walks the DOM tree, so unless you want to seriously rework your code you need to stick with that. What you will be
> doing is walking the DOM tree and then 'looking up' the associated > node in the GVT tree (under 'root').
I have no problem with reworking the code (it isn't mine anyway :-)
What would be the best way to walk the GVT tree and extract the outlines of the shapes? Can I still get to the "href" and "id" attributes? Do I have to do my own clipping with the AOI?
I will try it and see :-) Is there any in-depth documentation that describes the functional relations inside Batik and its rendering process?
One issue is if the transcode method 'imports' the given Document I'm not sure you can access the imported Doc (you could use BridgeContext.getElement(root) to get the root DOM Element I suppose)
In my application I'm parsing the file into a SVGDocument anyway (to get width and height) which I then pass to the transcoder.
Thanks
Robert
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
