![](https://secure.gravatar.com/avatar/b47d036b8f12e712f4960ba78404c3b2.jpg?s=120&d=mm&r=g)
2014-02-26 17:32 GMT+01:00 Jon Cruz <jon@...18...>:
On Feb 25, 2014, at 8:58 AM, Martin Owens wrote:
On Mon, 2014-02-24 at 23:51 -0800, Bryce Harrington wrote:
- Remove dom/ directory
This directory contains strange code which is barely used. The only class which is actually used is the URI class.
That's worth knowing, I'll hack that up in my branch as I add the data uri support.
Actually the intent of this one had been explained to others in the past. The dom directory was done in preparation of improving the extension system by providing a live DOM interface to plugins. We've even had members of the SVG and XML committees review and endorse the approach.
The approach taken in the dom/ directory is totally wrong. It attempts to create yet another tree which is live-updated from the SP tree. The correct way to do this is to bind the actual SP objects to the DOM interfaces. Moreover, this work was nowhere near completion, since the essential part - how to present any kind of API to the extensions, so that they can directly modify the document rather than operating on its XML serialization - was never done.
Moreover, the DOM APIs defined in the SVG specification are very limited and do not provide any facilities to conduct geometric calculations. For example, they don't define any geometric primitives which are not elements.
Regards, Krzysztof