>> I would like to see a poll of current users and developers for determining >> the primary focus:
My personal feeling is that everything up to ns4.7 type browsers is dead and to develop for these browsers I feel is pointless. I have no plans for the IOS library or VDE to have backward compatibility to older browsers. A project like VDE (I believe) will never work in NS4.7 or MacIE5, and I/we should not spend trying to make it sorta work. There is just some things that those browsers where not meant to do and if you push them to hard they will totally slow down they system, freeze or you guest it... crash. Leaving the user with a bad DynAPI taste in their mouth. Other then that I'm in total agreement with Leif. DynoAPI funny :) Stay healthy :) Michael Den 03-10-23 16.08, skrev "Leif W" <[EMAIL PROTECTED]>: > 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 ----- >> From: C Kissinger <mailto:[EMAIL PROTECTED]> >> To: [EMAIL PROTECTED] >> 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 >> >> >> ------------------------------------------------------- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://www.mail-archive.com/[EMAIL PROTECTED]/
