Hi Urs,
Urs Reupke wrote:
I do not, however, understand exactly what I have done by creating the BridgeContext and calling GVTBuilder.build -
do you know about the details and could possibly explain what happens within the program?
Up to know, I thought GVT was an internal representation of
my SVGs, one that I did neither need, nor was meant, to care about.
What you have done is built the GVT tree for the SVG Document (as well as doing all the CSS stuff). Without the GVT tree, which handles all the rendering, we can't provide much of the SVG DOM as most of it deals with the geometry. When you ask for the bounding box (or text length) from the DOM it calls over to the GVT tree (through the SVGContext) to get the answer.
We don't build the GVT as soon as you parse the document partly because we need/want extra information (like the UserAgent), and partly because there are cases where you might want to just use it as Core DOM for a while before turning on SVGness (for example for use with XSLT).
In general you can just ignore the GVT tree, but if you want to use SVG DOM methods you must construct it.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
