Hello Dan, It's very good to hear from the initial creator of this amazing API.
The problem I'm having is not only related to widgets, but o layers on a whole. It's just taking far to much time to create a few layers. As I've stated earlier I tried to create 40 basic layers (without any events)and the time taken was just not acceptable for web apps. After looking some more into the core of DynAPI I've found out that a lot of stuff goes on when the addChild() function is called. The API checks for children, invoke events that aren't used and perform various loops. The other down side to the API is when the page is been unloaded. It goes out and destroys all the existing objects before unloading the page. Is that necessary? Anyway, I'm looking forward to the improvements and will in every way possible try to help with the improvements of the DynAPI library. Best regards Raymond --- Dan Steinman <[EMAIL PROTECTED]> wrote: > If speed is an issue for you, and cross-browser > isn't, but you still want to build widgets with > DynAPI then do as someone else suggested - build the > main structure as a DynLayer inherited object with > browser specific contents. There's nothing stopping > anyone from building browser specific widgets in > fact I encourage it and will be trying to optimize > the DynAPI for this type of widget building. > __________________________________________________ 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
