I first started using
DynAPI because I needed a cross-browser solution for consistency across
DOM/non-DOM browsers in ecommerce web apps. This seemed to have been the
original focus
with CBScript and DynAPI2, but lately the focus seems to have changed to more
of an advanced
app factory (still a good thing).
I am still busy trying
to port DynAPI3 Oct. 4, 2003 snapshot for backwards compatibility with
NN4.03 and IE4, which when it is finished will probably serve me well into the
distant future as a browser paleontologist.
I would like to see a
poll of current users and developers for determining the primary focus:
advanced functionality vs. wider cross-browser support. With the DOM, anything is
possible, so
the need for a
JS wrapper API becomes less imperative. DynAPI has been great for both so
far, but I see
people wanting to move forward and drop support. I can't do that, but I'm sure
DynAPI will
still be great either way.
Thanks!
Christopher Kissinger
|
- Re: [Dynapi-Dev] Old Browser Support C Kissinger
- Re: [Dynapi-Dev] Old Browser Support Doug Melvin
- Re: [Dynapi-Dev] Old Browser Support Raymond Irving
- Re: [Dynapi-Dev] Old Browser Support Raymond Irving
- RE: [Dynapi-Dev] Old Browser Support C Kissinger
- Re: [Dynapi-Dev] Old Browser Support Doug Melvin
- [Dynapi-Dev] Object / Widget documentation Daniel Tiru
- [Dynapi-Dev] Object / Widget documentation Daniel Tiru
- RE: [Dynapi-Dev] Old Browser Support Raymond Irving
- Re: [Dynapi-Dev] Old Browser Support Kevin