Hi, Ted.
I wasn't sure of the exact mechanism... But, yes, definitely this is the way to do it. Expose just the DOM stuff to the outside world, with an org::w3c::dom::Node* referring to the "root" of the Inkscape application. Expose this single global with a function like "getInkscapeRootNode()"
Doing this, we would have linking deps from inkscape->dom, but none from dom->inkscape, so that we can expose internal functionality without exposing internal symbols. We could then finally get rid of the "cascading dependencies" which are plaguing us so badly right now.
Bob
Ted Gould wrote:
Bob Jamison wrote:
This morning I committed most of the DOM source to src/dom. I spent the rest of the morning removing warnings, and getting the compile to work nicely on win32. I will add the Makefile_insert when I get a chance. Until it is hooked up to the autotool tree, it should not hurt anyone's build.
I included the .idl's, so that people can see how the main .h's try to follow the w3c specs.
Now that it is committed, its glaring unfinished-ness will coerce me to work on it until it is done. :-)
Bob,
Are you planning on doing the win32 dll magic so that we can use this API with loadable modules?
--Ted