View states let you vary the content and appearance of a component or application, typically in response to a user action.
For example, the base, or default, view state of the application could be the home page and include a logo, a sidebar, and some welcome content. When the user clicks a button in the sidebar, the application dynamically changes its appearance, meaning its view state, by replacing the main content area with a purchase order form but leaving the logo and sidebar in place.
Transitions define how a change of view state looks as it occurs on the screen. For information on transitions, see Using Transitions.
About view states
In many rich Internet applications, the interface changes based on the task the user is performing. A simple example is an image that changes when the user rolls the mouse over it. More complex examples include user interfaces whose contents change depending on the user’s progress through a task, such as changing from a browse view to a detail view.
View states let you easily implement such applications.
At its simplest, a view state defines a particular view of a component. For example, a product thumbnail could have two view states; a default view state with minimal information, and a “rich” state with links for more information.
To create a view state, you define a default view state, and then define a set of changes, or overrides, that modify the default view state to define the new view state. Each additional view state can modify the default view state by adding or removing child components, by setting style and property values, or by defining state-specific event handlers.
Regards,
Ashok
