Well, do you have any suggestion for speed improvements for DynAPI? Will your API be available to the public?
You see, I really like the coding structure use by DynAPI. It's very easy and fun to work with. Widgets are very easy to create and understand. DOM-API looks good but it's coding structure is different from DynAPI. I only wished that they had made to coding structure DynAPI compatible :( I'm planning on creating some new widgets that will change the way web applications will ever look. My only draw back is the time DynAPI will take to create the widgets due to fact that it's not optimized for speed (as it relates to the creation of DynLayers). Is it wise idea to use stick with DynAPI. Will it be supported in future? If so what can we look for? --- Bart Bizon <[EMAIL PROTECTED]> wrote: > I have an API which will be part of a cross-browser > framework, which already > is lightyears faster and more robust then DynAPI. > Creating 1000(!) layers with HTML and set > properties, with a 600 mHz laptop > in about: > 4000 ms - IE5 > 9000 ms - IE4 > > Netscape is still to be optimized, but previous > results were at about 20 > seconds. __________________________________________________ Do You Yahoo!? Listen to your Yahoo! Mail messages from any phone. http://phone.yahoo.com _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dynapi-dev
