This is one of those very difficult questions to answer because it depends on a lot of factors. WebMaker pages are 'thin', consisting of HTML, CSS and Javacript and there is no theoretical limit to the number of controls, but the performance and usability of your application can be affected by some of the following factors:
The amount of resources available on the client and server machines.[/*]
Types of controls that are being used. For example, some controls will be more reliant on server processing to populate and determine their behaviour, whilst others will generate more client markup and associated script. Also, the resource requirements for some controls will vary depending on which features are turned on (conditional visibility for example).[/*]
Whether controls are 'overriden' with other frameworks such as Dojo using custom attributes.[/*]
The amount of server processing you need to do to populate and process the data for the control. So, for example, if you return a very long list for a drop-down instead of shorter blocks from a database or remote service, then the performance will be impacted.[/*]
Whether you are caching the data for some of the controls and the context of the cache.[/*]
The size of the user community and usage profile.[/*]
Any additional custom scripting introduced for individual controls or groups of inter-dependent controls[/*]
I know some of this is not directly linked to controls, but they affect the performance and behaviour of your page. This means there may be no technical issues related to positioning a large number of controls on a single page, but the performance may be impacted if the server-bindings are significantly complex.
Some of this also depends on the definition of a single page. You should try and design larger pages by combining partial pages if possible to help with the performance of the application and also longer term change management if performance does become an issue.
This is one of those very difficult questions to answer because it depends on a lot of factors. WebMaker pages are 'thin', consisting of HTML, CSS and Javacript and there is no theoretical limit to the number of controls, but the performance and usability of your application can be affected by some of the following factors:
The amount of resources available on the client and server machines.[/*]
Types of controls that are being used. For example, some controls will be more reliant on server processing to populate and determine their behaviour, whilst others will generate more client markup and associated script. Also, the resource requirements for some controls will vary depending on which features are turned on (conditional visibility for example).[/*]
Whether controls are 'overriden' with other frameworks such as Dojo using custom attributes.[/*]
The amount of server processing you need to do to populate and process the data for the control. So, for example, if you return a very long list for a drop-down instead of shorter blocks from a database or remote service, then the performance will be impacted.[/*]
Whether you are caching the data for some of the controls and the context of the cache.[/*]
The size of the user community and usage profile.[/*]
Any additional custom scripting introduced for individual controls or groups of inter-dependent controls[/*]
I know some of this is not directly linked to controls, but they affect the performance and behaviour of your page. This means there may be no technical issues related to positioning a large number of controls on a single page, but the performance may be impacted if the server-bindings are significantly complex.
Some of this also depends on the definition of a single page. You should try and design larger pages by combining partial pages if possible to help with the performance of the application and also longer term change management if performance does become an issue.
RE: Max No of Controls
This is one of those very difficult questions to answer because it depends on a lot of factors. WebMaker pages are 'thin', consisting of HTML, CSS and Javacript and there is no theoretical limit to the number of controls, but the performance and usability of your application can be affected by some of the following factors:
I know some of this is not directly linked to controls, but they affect the performance and behaviour of your page. This means there may be no technical issues related to positioning a large number of controls on a single page, but the performance may be impacted if the server-bindings are significantly complex.
Some of this also depends on the definition of a single page. You should try and design larger pages by combining partial pages if possible to help with the performance of the application and also longer term change management if performance does become an issue.
Kind Regards
Abdul
RE: Max No of Controls
Thanks Abdul