I have been working on converting an extremely large Web 1.0 project to Web 2.0. I have made a lot of progress and have learned a lot. There are a lot of things that are broken. I want to have a discussion on some of the speed issues of Web 2.0 and hopefully find some insight into how I can refactor some of my code.
I have a WebPage class that embeds about 7-9 WebContainer classes, each of those WebContainers have a WebListBoxes, and maybe 3-5 more embedded WebContainers with more WebListBoxes and HUNDREDS of custom WebUISDKControls that mimic WebTextFields (so I can have an EnterKeyPressed event).
This WebPage takes approximately 3-4 minutes to render on the screen. It takes about 1 minute for the screen to go white, then about 2-3 minutes more for it display any of the content.
Compared to Web 1.0
In Web 1.0, this same WebPage takes about 1.5 seconds to load.
What are some of the controls that you have identified as causing speed issues? Additionally what have you discovered are good practices for loading things on screen? Like should we avoid using the .style property on controls? (I have hundreds of these modifications to make things Look right such as positioning toolbars)? Are using WebSDKUIControl actually the problem? Should wait for “Shown” to modify .style? Should I avoid using WebListBoxes?
If anyone has any idea where my bottleneck might be, I would love the tips so I can run better tests.
For those of you who have not yet converted your large project to Web 2.0. I sincerely believe you should NOT do it now. The number of issues that need to be fixed in the Conversion process alone are insurmountable and frustrating.