Bob Jamison wrote:
I would like to amplify that, going so far as saying that any major API item should be separated into interfaces and implementations; the interfaces being pure virtual with -NO- link dependencies. This is help in:
o Reducing compile times o Alleviating cascading link dependencies o Scripting (binding a scripted object to an interface) o Allow clean exporting of an Inkscape API.
I'd also want to push for everyone doing any of this to keep the 'standards' in mind.
That is, reference all the DOM specs and their friends.
DOM Level 2 Core Java binding http://www.w3.org/TR/DOM-Level-2-Core/java-binding.html DOM Level 2 Core ECMAScript binding http://www.w3.org/TR/DOM-Level-2-Core/ecma-script-binding.html
DOM Level 2 Events Java binding http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113/java-binding.html DOM Level 2 Events ECMAScript binding http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113/ecma-script-bindin...
DOM Level 3 Events Java binding http://www.w3.org/TR/DOM-Level-3-Events/java-binding.html DOM Level 3 Events Java binding http://www.w3.org/TR/DOM-Level-3-Events/ecma-script-binding.html
SVG Animation DOM interfaces http://www.w3.org/TR/SVG/animate.html#DOMInterfaces
XForms http://www.w3.org/TR/2003/REC-xforms-20031014/ http://xformsinstitute.com/essentials/
etc.