I've got a record with a lot of fields to edit. I'd like to edit it on a single .aspx page, so that state can be maintained entirely by the postback/viewstate model.
One approach to do this is, if the form could be subdivided into 4 logical forms, for example, then we have 4 tabs on the form. We also have 4 panels, each panel holding the controls for the respective tab. A placeholder control is on the page in the location where any one panel would be displayed. To make the page easier to edit in VS.NET, we keep the 4 panels elsewhere on the page, so that they don't all try to occupy the same space. At runtime, we add the 4 panels to the placeholder control, in the same order each time so that ViewState is restored correctly. Finally, depending on the active tab during a given postback, we only make one panel visible, matching the selected tab. The other panels are not visible. I know having lots of controls on a page slows down performance a lot. My question is, does it make a difference if we're talking about a normal amount of visible controls, plus 3 or 4 times as many invisible, non- rendered controls? Or are a lot of controls bad, either way? In other words, how much of a perfomance hit are we looking at to have a page that has lots of controls (bad) but that only makes visible 1/3, 1/4, or 1/5 of those controls at any time (but still maintains viewstate for all the page controls)? Thanks. Kyle Clarke [EMAIL PROTECTED] You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
