I'm sure there have been numerous responses to this email,
but I am just back after a week of using the DynAPI in a 22 million$
product..
They had never considered using any DHTML library and where surprised at
the capabilities to say the least.
About Strider's messag:
1) Code-Branching: While th
> 1) TREE-BRANCHING the API. This includes splitting the current offering
> into NS/IE legs as well as adding a new "DOM" leg. This doesn't imply
> extending the current API into the DOM branch as much as using the same
> "interfaces" for the object/method/property calls while implementing
> int
