Forgot your password?
New user?
Document Actions
#188: Configurable content views
- Contents
- Proposed by
- Malthe Borch
- Proposal type
- Architecture
- State
- draft
Motivation
The motivation for this PLIP is to facilitate true separation of content and presentation by supporting configurable content views.
Consider a collection of objects as a content object. The object will probably have a title, a description and a reference field. There are quite a few ways of displaying this collection if we support looking into the referenced objects. If the objects have images, a configuration option on the view could decide whether to display that image.
Having multiple views via CMFDynamicViewFTI does not solve this problem, although it's a step in the right direction.
Proposal
This PLIP naturally only applies to content views that are directly connected to a view class.
On the view class side, a configuration view needs to be provided, either by way of formlib or a similar library or through a custom template.
The configuration itself would need to be annotated onto the underlying content object.
On the UI-side, a 'configure' option would need to be added to the display menu for views provided a certain interface.
Implementation
To do.
