Regarding old browsers or new browsers... if you need some support for a browser, knock yourself out and write it.  :-)  Hopefully the support for all browsers can coexist within the API?  Or does the backward compatibility (adding all the return values, etc, for NN 4.03) break the newer browsers?  If so, maybe there's a need to split support into two flavors?  DynAPI for current / modern browsers, and err, how about DynoAPI for the Dinosaurs.  ;-)
 
Leif
----- Original Message -----
Sent: Wednesday, October 22, 2003 1:41 PM
Subject: [Dynapi-Dev] Old Browser Support

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
Web Development Consultant

 

Reply via email to