This topic describes how to create views. A view is composed of a view definition that defines the basic structure and components that plug in to areas. The view and component definitions define basic behavior and a client-side widget that is responsible for creating the user interface.
See the following example implementations:
When you load a view, the following flow is triggered:
You can alter the content of a view, plug in a component into a container. The component definition describes strings with the plug-in paths, or areas, that the component can plug into automatically. If any of these paths matches the PlugInPath property of a panel, then the component is created and added to the container.
After you add the components to the containers, a chain of view transformers are applied to the view. A view transformer alters a view before it is rendered by adding or removing components. Episerver provides a few default view transformers, but you also can add your own.
The default view transformers are:
The following image shows how the view (with four pluggable areas) is assembled on the server.
Components that want to plug into areas are added automatically to one or several of their respective areas.
Configuration adds and removes components for the different panels. This configuration is done per view but you also can configure a specific component to replace another component globally through the IOC container.
If the view contains personalizable panels and the user has personalized these the contents for the panel is replaced with the personalized content.
Last updated: Oct 27, 2016