On Tue, 2005-08-30 at 21:38 -0500, aaron@... wrote:
> Tell me if I've got the wrong idea, but I've been looking forward to=20
> internal extensions cause I want extensions to have access to the same=20
> sorts of things users have access to in the gui. like boolean ops,=20
> simplfy, etc. And having access to some of inkscapes powerful internal=20
> path structures would be amazing too.
Well, I think you have the wrong idea :) At least for now.
What DOM will provide first is just an access into the SVG Document
Object Model. This is roughly the same as taking the SVG and loading
into a DOM based implementation in Python (or any other language). The
improvement here will be that the serialize, expand, serialize, expand
steps into the different models won't exist like they are today with
Now, that isn't to say that other internal Inkscape functions won't be
available, it is just not something that is available by just having
DOM. I think I can say for sure that a script will be able to activate
any verb, that's pretty easy and would be an easy to support API. The
problem is that when we add more stuff, we have to support it, ideally
for a long time. So, I'm sure there will be lots of flames on this list
about what should go into the API and what shouldn't, but that hasn't
happened yet (and doesn't need to happen yet either).