Page History
...
- Level 1: Make selection JCR agnostic
Jira server Magnolia - Issue tracker key MGNLUI-2657 - generalize JcrAdapters into Vaadin Items
- generalize String ids into Object itemIds
- Handle multiple selection nicely (e.g. avoid converting sets into lists, items to itemIds)
- try not to use Items when itemId is sufficient (events)
- No big API breaking
- Level 2: Redefine Browser / Workbench apis
Jira server Magnolia - Issue tracker key MGNLUI-2569 - define responsibillities
- diagram appreciated
- first concrete implementation is JCR
- also focus on a different implementation (FileSystem, Bean) to uncover potential problems
- try to include proposal #6 (e.g. exposing Workbench presenterClass)
- Level 3: Dialogs and DetailSubApps
TODO StoryJira server Magnolia - Issue tracker key MGNLUI-2656
- Level 4: Redefine ContentPresenter apis
Jira server Magnolia - Issue tracker key MGNLUI-2658 - TODO Story
- make content views less workbench and JCR dependent
- container properties / operations may belong to workbench
- VS. list only requires visible columns, width...
- one should think about filters upfront
- think about facets at workbench level
- Further independent enhancements
- Workbench filters (dynamic / permanent)
- TODO Story in Ideas
- Single JCR Container
TODO Story in IdeasJira server Magnolia - Issue tracker key BL-153
- Support for federated workbench / actions / search
- Workbench filters (dynamic / permanent)
- We don't affect JCR adapters
...
Overview
Content Tools