When writing for the DOM browsers, most of the DynAPI we have now is a waste. Creating an API for DOM browsers would/should most likely not be compatible with the current version. Implementing an API for DOM browsers can be done in a much simpler/powerful manner. I'm currently using an API I wrote that is less than 100 lines and just as powerful as the DynAPI. -- Robert Rainwater On 5/18/2001, 5:29:53 AM EST, Sergi wrote about "[Dynapi-Dev] Development Direction": > Totally agree. Not-DOM Browsers support in a separate js _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dynapi-dev
- [Dynapi-Dev] Development Direction Scott Bristowe
- RE: [Dynapi-Dev] Development Direction Eytan Heidingsfeld
- SV: [Dynapi-Dev] Development Direction Scott Bristowe
- RE: [Dynapi-Dev] Development Direction Digital Strider
- RE: [Dynapi-Dev] Development Direction Sergi Mansilla
- Re: [Dynapi-Dev] Development Direction Richard Bennett
- RE: [Dynapi-Dev] Development Direction Digital Strider
- RE: [Dynapi-Dev] Development Direction Cameron Hart
- Re: Re[2]: [Dynapi-Dev] Development Direction Robert Rainwater
- Re: Re[2]: [Dynapi-Dev] Development Direction Richard Bennett
- RE: Re[2]: [Dynapi-Dev] Development Direction Digital Strider
- RE: Re[2]: [Dynapi-Dev] Development Direction Digital Strider
- Re[4]: [Dynapi-Dev] Development Direction Robert Rainwater
- RE: Re[4]: [Dynapi-Dev] Development Direction Eytan Heidingsfeld
- RE: Re[4]: [Dynapi-Dev] Development Direction Eytan Heidingsfeld
- RE: Re[4]: [Dynapi-Dev] Development Direction Digital Strider
- Re: [Dynapi-Dev] Development Direction Michael Pemberton
