Details
-
Story
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
None
Description
User Story:
As a developer or business analyst, I want to easily specify details for how the controls should be presented in the GUI, so that I can succeed in fulfilling my business requirements.
With current state of CT, the model definition is very easy and clear, but if a developer needs a small modification to the UI it is confusing because they need to provide configuration in a confusing way in an app definition file.
Its important that evaluators are not confused or disappointed by complexity of common CT-related tasks in Magnolia, compared to our competitors products.
Acceptance Criteria:
- Developer can tune the GUI of the controls in the same file as the CT model definition.
- Controls are tuned with the same properties as the normal FieldTypeDefinitions.
- The following GUI items can be achieved:
- Field types
- Tags
- Twin Column (Multiselect)
- Option group (Radio buttons)
- Password
- Code
- Validation
- HTML validation (email, phone, etc)
- Rows property for Text input.
- Tuning content previews (contentPreviewDefinition)
- Specify "targetTreeRootPath"
- Specify "fieldEditable"
- Field types
Some things would ideally be tunable with CT - but dont make sense to tune in a "presentation" context because they actually affect the data model. Such as:
- Tuning data storage (identifierToPathConverter)