You wrote: >What good is a pickup-minivan if it doesn't have >sufficient horse power? The analogy is interesting considering the 200(Mhz) "horse power" engine used for testing. I would imagine the response on any dynamic graphic program (such as today's more modern games or flash applications) is equally slow. My worst case test environment is a PII 133mhz w/64Mb and carefully designed dynlayers work fine once loaded. I expect slow response on this machine. Much of the slow response can be duplicated outside of dynapi. Try generating a page of equal complexity using JavaScript. I have a bare bones non-dynapi DHTML pagination script that generates a tabled report of spreadsheet data. I built it without DynAPI, then with DynApi. With 1000 rows (6 col) paginated into 20 script generated tables contained inside generated page divs the response time is the same. The difference is what I can then do to the DynLayer exceeds anything I can then do to a plain old div without a ton of coding.
-----Original Message----- From: Raymond Irving [mailto:[EMAIL PROTECTED]] Sent: Friday, September 28, 2001 11:28 AM To: [EMAIL PROTECTED] Subject: [Dynapi-Dev] Speed Test! Does DynAPI Qualify? Hello Everyone, I must salute the creators of DynAPI for creating such a fascinating API. I really like the object structure and it's easy-of-use. But there's something that I'm concerned about, and that's speed! What good is a pickup-minivan if it doesn't have sufficient horse power? After doing some testing on my pentium 200 (yes 200 MHZ) using IE5.0, I've found DynAPI to be very slow when creating x number of layers. example: for(var a=1;a<=2;a++){ y=y+22 for (x=1;x<=20;x++){ myLayer = new DynLayer(null,21*x,y,20,20,"#C0C0C0") DynAPI.document.addChild(myLayer) } } The above code will create 40 layers within 1-2 seconds. The more layers you add the longer it will take to create another 40 layers. In other words, if you should have say 100 layers on screen and then try to add another 40, its takes a longer time to add the 40 layers than it would at the beginning. I've also noticed that a page takes a very long time to unload or reload if there are a lot of layers on the screen. The findLayers() function is just as slow when trying to find x number of inline layers. Layers are the heart of DynAPI. They're used in about 99% of the objects created for use with the API. For example let's say I want to create a dynamic web form that uses 40 Labels. With each Label using at least 2 DynLayers it who take a normal computer a very long time to generate the 40 Labels (80 layers), not to mention Buttons and other widgets that I may use. The long and short of it is that DynAPI really needs to do something about the speed at which layers are created and the amount of browser-resources to maintain a layer. A true state of the art web application will use over 100 layers at any one time. As a result of this a few questions come to mind: 1) How long will it take for DynAPI to create x number layers? 2) How many layers can DynAPI handle before slowing down the creation of over layers? 3) How long will it take for DynAPI to unload a page? If any one knows of a way to speed up layer creations please let me know about it. P.S. I do hope the developers are on this list. Best regards, Raymond __________________________________________________ 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 _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dynapi-dev
