Page History

...

• Propagate Vaadin selection transparently up till action execution
  
  • as a Vaadin Item or a Set of Vaadin Items 
    
    • so that executor doesn't care about data source
• Map Vaadin Items to ItemIds to Human-readable location at Browser level
• Split WorkbenchDefinition from JcrWorkbenchDefinition
  
  • Configure a containerClass in code - can be overridden in config
  • Have a JcrBrowserSubAppDescriptor that overrides #getWorkbench() with JCR specific workbench definition type 
• Unify all JCR Containers at workbench level
  
  • They represent the same data set
  • JCR is by nature Hierarchical, Indexed and Ordered
  • Advanced behaviors can surely be delegated to smaller units (search, filters)
  • Thumbnail resolution is not among container duties
• Research how a ContentPresenter can start with just ContentPresenterDefinition and Container to populate itself
  
  • avoid to carry WorkbenchDefinition along everywhere
  • in a similar fashion as DetailPresenter#start(EditorDefinition, JcrNodeAdapter, ViewType)  
• Restructure ContentPresenter and Workbench definitions
  
  • editable and dragDropHandler belong to content views - they do not necessarily apply to all
  • columns should belong to a ListPresenterDefinition interface - they do not apply to thumbnails or any arbitrary other content view
• Expose expose preconfigured presenterClassfor browser / workbench / actionbar
  
  • so that customization doesn't always have to start at subApp level
• We proceed without affecting JCR adapters

...