Well I got the examples from Create Layer to Hover Animation in that snapshot to work in old browsers now (except TabManager because my laptop doesn't have a separate numeric keypad with arrows), but one major stumbling block which maybe someone can answer. In NN4.03 almost all examples shoot a "JavaScript Error: too much recursion" onmousedown and onmouseup in document areas of the page. Two of the same error for every click. Any ideas?
Christopher Kissinger Web Development Consultant >>> -----Original Message----- >>> From: [EMAIL PROTECTED] >>> [mailto:[EMAIL PROTECTED] On Behalf >>> Of Raymond Irving >>> Sent: Wednesday, October 22, 2003 4:09 PM >>> To: [EMAIL PROTECTED] >>> Subject: Re: [Dynapi-Dev] Old Browser Support >>> >>> >>> >>> I say we also try and include NN 4.03 but it's just >>> that NN4.03 has a major problem with functions not >>> return a value. >>> >>> "With the DOM, anything is possible, so the need for a >>> JS wrapper API becomes less imperative." >>> >>> I don't think so! I thought that DOM-Browsers would >>> make DynAPI go away but I was wrong. Over the past few >>> months I've had nightmares trying to get apps to >>> display and work the same in all three of the major >>> browsers. >>> >>> -- >>> Raymond Irving >>> >>> --- C Kissinger <[EMAIL PROTECTED]> wrote: >>> > 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 >>> > >>> > >>> > >>> > >>> > >>> >>> >>> __________________________________ >>> Do you Yahoo!? >>> The New Yahoo! Shopping - with improved product search >>> http://shopping.yahoo.com >>> >>> ------------------------------------------------------- This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100 http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://www.mail-archive.com/[EMAIL PROTECTED]/
