I have a somewhat complex dialog box that I use for program settings. There's a list view on the left and a tab control on the right. For each entry in the list, there's a separate copy of the tab control. There are four tabs in each tab control. So there are a total of 16 tab panes. (Of course only one is visible at a time.)
This dialog takes over 15 seconds to come up on a Xeon 5160 running at 3Ghz. I know IE7 is inherently slow, but this seems truly remarkable. Under IE8 on a Core i7, the dialog comes up in under a second. It seems like something is going on that's trigger nonlinear behavior in IE's DOM model. Do QooxDoo veterans see this kind of slowdown with IE7? Is it just that there are too many tab panes? Is there some way to precompute a DOM tree so that it doesn't have to be built dynamically every time I call up the settings dialog? (I'm sorry if this is a bit short on details; I can't easily factor out the code to make a nice demo of the problem right now, but I thought it was better to post something than not.) Dave -- View this message in context: http://www.nabble.com/IE7%3A-dialog-takes-15%2B-seconds-to-come-up-tp23723455p23723455.html Sent from the qooxdoo-devel mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
