I am writing an asp.net application, I must include that page where the user can add an item in which many There are sub-sets, each of which is unlimited, the subtitles are between 10 and 15 fields, so a fair bit of UI space is required.
An example of what I mean, a user must be able to add business records to the system, including employee records and any number of asset records.
The way I usually do this, it's using multivise control with a set of tabs located at the top. Tabs switch between the view of the polyview. The first tab will be for the business record, the second will be for the record, and the third for asset records. For adding employees and assets to a new employee (or asset), initially there is an empty strip when this button is clicked, the page is posted back and the employee (or asset) to capture the details User control is dynamically added.
A save button that stores the whole object graph in the database.
This is quite complex to maintain and maintain and I usually face headache to manage viewstate for dynamic user controls. Obviously, the viewstate on the page can be quite large, causing the page to slow down significantly.
The advantage of this is that the user has a very intuitive UI to understand, and the user can add everything and check it all before saving anything from the database.
Can you please suggest any other UI patterns that you can use for this and any benefits or disadvantages?
Thanks
/ P>
If you are not MVC without state, then you are considering the following tips:
- Disable viewtest on non-reference elements (i.e.: label) / li>
- Compress the viewsto by defining a custom handler that bzips> base64 encodes
- Store the viewstate on the server, create a request id, and tie the id in the app cache with the sparse window = for session life span (non-sliding), then with your guidance ViewState Change back and forth to Cheers, Florian
Comments
Post a Comment