...
| Mockup | ||||||
|---|---|---|---|---|---|---|
|
editTabOverview.cfm
This is the specialised webtop controller for rendering the "webtop overview" view layer. This works out what version of the object to render, adds a webtop header and footer for the page. There should be no reason at all to modify or change this file.
types.webtopOverview
A types or generic webskin based in ./farcry/core that is available to all content types. Responsible for rendering the entire webtop overview screen. By default this calls several other webskins (or views), and renders default formatting based on content type system attributes.
You can override this view in your project or plugins as required. However, we would recommend leaving the view as is in the majority of cases and working instead with types.webtopOverviewActionPrimary and types.webtopOverviewSummary to modify behaviour. This ensures a consistent structure to the webtop overview across content types.
types.webtopOverviewActionPrimary
The webtopOverviewActionPrimary generates the various primary calls to action for the specific content type in question. Its a fairly complicated view that works out what actions should be permissible based on the users permissions and the current state of the underlying object. It's not for the faint hearted but is isolated so that developers can integrate their own actions as needed.
Override the webskin in your project or plugin by creating a webskin of the same name under the webskins sub-directory matching your typename. For example, the News Content type (called dmNews) would have a webskin called ./webskins/dmNews/webtopOverviewActionPrimary.cfm
farWorkflow.renderWorkflow()
The function integrates the FarCry workflow sub-system if it has been activated for the application. If you haven't activated the workflow sub-system just ignore this option.
types.webtopOverviewSummary
The webtopOverviewSummary should be used as the primary point of customisation for different content types.
Override the webskin in your project or plugin by creating a webskin of the same name under the webskins sub-directory matching your typename. For example, the News Content type (called dmNews) would have a webskin called ./webskins/dmNews/webtopOverviewSummary.cfm
Special Situations
Navigation Folders
...