Visual WebGui - A unique approach to AJAX development
page 2 of 4
by Guy Peled
Average Rating: This article has not yet been rated.
Views (Total / Last 10 Days): 21158/ 15

Visual WebGui Developer Guidelines

·         Visual WebGui automatically detects components that need to be updated, updating the most granular change possible for the updated component.  By updating only required components users can optimize application performance and bandwidth usage.  For example, updating a list view item should be preferred over updating the full list view since Visual WebGui can send only the changed list view item and redraw only that item.

·         Visual WebGui automatically queues unhandled events for post back optimization.  Developers should remove unused event handlers or consider using their queued version.  By definition every event handler that does not interact with the user is a potential candidate to be attached to the queued version of the event.

·         Visual WebGui modal dialogs are only modal on the client side as opposed to WinForms implementation and dialog.  Results should be retrieved by attaching to the closed event.

·         Visual WebGui can have more than one root form as opposed to WinForms implementation.   Each root form is mapped to a virtual WGX URL in the application configuration file.

View Entire Article

User Comments

No comments posted yet.

Community Advice: ASP | SQL | XML | Regular Expressions | Windows

©Copyright 1998-2024  |  Page Processed at 2024-04-18 5:48:51 AM  AspAlliance Recent Articles RSS Feed
About ASPAlliance | Newsgroups | Advertise | Authors | Email Lists | Feedback | Link To Us | Privacy | Search