Hi Thomas.
Now that the svn migration is done, I was thinking about (carefully)
merging in the svg12 branch code into the trunk. Since there's a been a
few changes since the branch I guess it won't be a simple diff to apply.
What do you think?
Also, I've changed my mind on how I think the DOM 3 interfaces should be
handled. I think it would be better not to include a copy of all of the
DOM 3 interfaces in org.apache.batik.dom.dom3 and rather just implement
and extend whichever level DOM interfaces are available. Since users of
the Batik DOM classes in environments where JAXP 1.3 isn't available
will have to cast the objects anyway, I think it would be better to have
them cast to the org.apache.batik.dom.* classes rather than the
org.apache.batik.dom.dom3.* interfaces. For example:
Node n = ...;
String base = ((AbstractNode) n).getBaseURI();
rather than
Node n = ...;
String base = ((org.apache.batik.dom.dom3.Node) n).getBaseURI();
Or if they don't like that, make them install the new xml-apis.jar in
the approved overrides place. Either way, Batik's actual DOM code won't
rely on the DOM 3 specific members of the interfaces.
For cases where constants are needed, they could be copied into the
concrete class, e.g. the DOCUMENT_POSITION_* constants could be defined
inside AbstractNode. (This shouldn't conflict with the constants
defined in the DOM 3 Node interface under JDK 1.5, should it?)
For cases where constants are defined in a class, such as the two new
exception codes in DOMException, I don't know where they should go to be
visible to JDK < 1.5 environments.
Your thoughts?
Thanks,
Cameron
--
e-mail : cam (at) mcc.id.au icq : 26955922
web : http://mcc.id.au/ msn : cam-msn (at) aka.mcc.id.au
office : +61399055779 jabber : heycam (at) jabber.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
