MenTaLguY wrote:
On Tue, 2004-08-17 at 15:29, Jon A. Cruz wrote:
But for the *what* to bind... enter DOM and it's friends (DOM Events, XPath, SVG DOM and some assorted other things like SMIL, XForms, etc).
The W3C has done some decent work here. We can use their IDL's and language bindings to tell us *what* our API should look like.
While I rather vehemently oppose using DOM for our internal representation (at least at the bottom-most level), I think it is the best choice for our externally visible APIs (at least as the preferred/straightforward option).
DOM's universality aside, one of the reasons for this is that over the next twenty releases or so the internal representation will continue going through some major churn. Having a stable external APIs is a good thing.
In the DOM I am making from the w3c idl's, I am going through a lot of extra effort to separate the interface definitions from the implementation. This is a very good example.. If IS's internal representation implementation ever changes from Repr to something else like AST, it would be good to be able to keep a steady API for our scripts & stuff.
I am almost done with a "default" DOM implementation, now I need to start on the repr-oriented implementation.
Bob