What is a Content View?
From Sense/Net 6.0 Wiki
Contents |
[edit] Overview
Content Views form the default way of displaying and editing Contents on the Sense/Net 6.0 Enterprise Portal. A Content View is a special ASP.NET user control, defined through an ascx file in the Repository, and contains Field Controls.
When a Portlet is about to render a Content, it usually starts by finding and loading the appropriate Content View.
[edit] Default Content Views
In Sense/Net 6.0, default Content Views can be defined for each Content Type. These are automatically loaded if no custom View is specified. Default Views for a specific Type reside in the folder /Root/System/ContentViews/<ContentType>/.
Note that there is no automatic fallback mechanism for Content Views based on Type inheritance. Eg. defining a View for the File Content Type doesn't define the View for its child Types, like Image. If you want a Portlet to display several Content Types with the same Content View, you need to explicitly set the View in the Portlet settings.
[edit] Views to be used in the Content Explorer
- New.ascx: Shown in the New Content dialog. The Content is not pre-existent when the View is loaded.
- Edit.ascx: Shown in the right pane of the Explorer, when opening a Content.
[edit] Views to be used on the Portal
- Browse.ascx: The default way of displaying a Content in a read-only way. This is the View you can use to show Contents to the general public. (Eg. showing an article to readers, as opposed to editors.)
- InlineEdit.ascx: This View is for editing a Content on the Portal interface.
- InlineNew.ascx: This View is for creating a new Content on the Portal interface. The Content is not pre-existent when the View is loaded.
- Query.ascx: This is the default View to display the Content in a list of query results, similarly to the search result list of Google.
