Page History

...

1. Level 1: Make selection JCR agnostic

   1. Jira
      server Magnolia - Issue tracker key MGNLUI-2657

   2. generalize JcrAdapters into Vaadin Items
   3. generalize String ids into Object itemIds
   4. Handle multiple selection nicely (e.g. avoid converting sets into lists, items to itemIds)
   5. try not to use Items when itemId is sufficient (events)
   6. No big API breaking
2. Level 2: Redefine Browser / Workbench apis

   1. Jira
      server Magnolia - Issue tracker key MGNLUI-2569

      
      
   2. define responsibillities
      
      1. diagram appreciated
   3. first concrete implementation is JCR
   4. also focus on a different implementation (FileSystem, Bean) to uncover potential problems
   5. try to include proposal #6 (e.g. exposing Workbench presenterClass)
3. Level 3: Dialogs and DetailSubApps

   1. Jira
      server Magnolia - Issue tracker key MGNLUI-2656

4. Level 4: Redefine ContentPresenter apis

   1. Jira
      server Magnolia - Issue tracker key MGNLUI-2658

   2. make content views less workbench and JCR dependent
   3. container properties / operations may belong to workbench
      
      1. VS. list only requires visible columns, width...
   4. one should think about filters upfront
      
      1. think about facets at workbench level

...