Haven't we dropped this yet? DynAPI thrives on it's ability to support 4.X - 5X (and 6x moslty) in Ns and IE.. Hell, I got my current contract on the strength of the DynAPI as a fulkly cross-browser library.
I can tell you right now, that I have yet to even hear of a contract not requiring backwards compatability. Concidering that 85% of my work comes from our government (Canadian) there is no way I can 'just drop' 4.X browsers.. you see, the Government of Canada has accessability guidlines for ALL WEb-based applications.. These guidelines call for a blind, on-handed, trained Chimp with a 386 and windows 3.1 to still be able to access the application. If you want 5+ Only support, go with domlib or it's kin. Can we drop this now? The last time we lost about 4 months of develompent because people just couldn't let this go. We are not now, nor will we be (in the near future) be dropping 4.x browser support from DynAPI. To do so would be to illiminate the only real selling point of the API, not to mention losing some developers who would otherwise be helping us make the DynAPI better and better.. > > ----- Original Message ----- > From: "Seamus Malone" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, November 08, 2001 3:16 PM > Subject: RE: [Dynapi-Dev] re: small poll > > > > no, i think i'm suggesting something different. i find that a lot of > things > > i'd like to do are just not supported by ns4 (post-render object > > naming/renaming, > > image re-sizing, sizing of relatively positioned layers) i have generally > > hacked my way around this, but it's not pretty and it's a lot of code... > > and both ie and ns crash when i have more than x layers dancing around. it > > may not have happened yet, but for projects 6mos to a year out that i have > > to put big cycles into i'm thinking of just not bothering to write for any > > 4.x browser. on the other hand i've written stuff based on the dynapi that > > i'd like to run in future version and not have to re-write or god forbid > > load > > two apis. the question then is how do you cleanly depricate a browser but > > not > > cut support completely. i don't think you have to write to different > > versions > > or a bunch of helper files for specific browsers. you could just freeze > ns4 > > development at a specific version and slowly cut it out of future > > versions... > > as you said this would really just be a search for is.ns4 references > anyway. > > then do a browser sniff and either import the files before or after a > given > > version. with the exception of some weirdness finding the x and y > > coordinates > > of images in ie5.x there are clean ways of getting similar behaviours out > of > > > > all the browsers. there are behaviours you just can't get at *all* out of > > 4.0 > > browsers... you can simulate them through positioning absolute layers, but > > that's a whole different bag of cats and a lot more work. > > > > i guess what i'm tying to do is to preserve work i've done as well as the > > rather > > impressive collection of third party widgets in dynapi as opposed to > > starting from > > scratch with a purely dom-based api. i kind of wonder how much any api is > > really > > needed if you have a pure cross browser dom... all the object references > > should > > be the same then anyway. not that MS would make it that easy, but in > > principle. > > > > sm > > > > -----Original Message----- > > From: Michael Pemberton [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, November 07, 2001 7:12 PM > > To: Seamus Malone > > Subject: Re: [Dynapi-Dev] re: small poll > > > > > > The code itself is already able to be written in a "browser-by-browser" > > fashion. The argument here should not be based around the ease of > dropping > > a > > browser. > > > > It is possilbe to remove a browser by simply doing a search for all > "is.ns4" > > (or > > is.mac, is.ie, is.ns6 etc) and removing the related code. This is not an > > issue > > related to this argument. > > > > This should be a decision based on other issues such as ease of > > administration, > > side effects, overheads and the like. For example: > > We already know that NS4 is slow with too many document.write > calls. > > Why create more? > > Different version of IE require different code in different parts. > > Do > > you suggest making an IE4/IE5/IE5.5/IE6 version? > > Mozilla and IE have some common code in some spots. How do you > > suggest > > allowing for this? > > > > If you plan on creating a version for each browser, does this means that > we > > need > > to copy the common code into each file? If so, who is willing to keep > track > > of > > ALL files to make sure that they are in sync with each other? > > > > These issues may not be a factor when you can pass on the costs to the > > client. > > But, in a project with no budget and limited, though highly dedicated, > human > > resources, these are MAJOR. > > > > > > > > _______________________________________________ > > Dynapi-Dev mailing list > > [EMAIL PROTECTED] > > http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/ > > > _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/
