Page History
...
| Pages | A delete | A preview | A edit | A export | A activate | A deactivate | A activateRecursive |
|---|---|---|---|---|---|---|---|
| no selection or root | |||||||
| any selection | x | x | x | x | x | x | only if no sub pages |
For redo/undo we will enable/disable based on the undo history size.
Configuration proposal
on each level, section, group, action, we need to configure three things:
- noSelection : true/false
- nodeTypes : list of supported node types
- property : true/false
if no constraints are configured for an action it takes the decision of the containing group, otherwise it takes its own decision
Problem
The action bar can take several states within one sub-app.
...
- Action bar definition should define two things:
- the structure: sections, groups, and all possible actions in these groups, in one single place. This ensures proper ordering of actions at all time
- the states that describe e.g. the section titles, the set of actions displayed, and potential substates. This mechanism should allow for additive composition of states (think of the use case for an optional AND editable area in page editor)
- Implementing context sensitivity then only means to configure these states properly and toggle between them.
It is likely that context sensitivity is not handled at all at the action bar level, but rather straight on the actions.- If so, the action bar definition is reduced to its sole structure.
- Edge case (page editor): do we provide a way to configure context-sensitive section titles?
Decision
-
Access Control
Determining wether the current user has access to an actions should be based on roles. We need to configure the required roles on the action definition.
...
Overview
Content Tools