Page History
...
- It is impossible to plug an external data source into the workbench
- One can perhaps extend our default content presenters
- TreePresenter, ListPresenter, ThumbnailPresenter, SearchPresenter
- The container implementations are hard-coded in there
- resp. HierarchicalJcrContainer, FlatJcrContainer, ThumbnailContainer, SearchJcrContainer
- Then one needs to extend all of these desired presenters to hook in external content
- And finally configure them as presenterClass on contentViews, or using custom ContentPresenterDefinitions
- And yet the Workbench and Browser sub-app will complain/crash because custom container items are not representing JCR items.
- One can perhaps extend our default content presenters
- Nor is it possible to filter JCR content easily
- Similarly as above, to implement a simple filtering mechanism for a JCR workspace, one must still extend and reconfigure all content presenters.
- e.g. security-app, forum moderation
- Similarly as above, to implement a simple filtering mechanism for a JCR workspace, one must still extend and reconfigure all content presenters.
- Workbench and Browser APIs are inherently tied to JCR
- Event the view implementations are depending on JCR/JcrAdapters (e.g. TreeViewImpl)
- WorkbenchDefinition may be reduced to the raw
- How about Location and path in the status bar when dealing with non-JCR items?
- One needs pluggable mechanisms to map these representations together:
- content as Vaadin Item
- content key (itemId) as provided by Vaadin Container
- content key as a human-readable variant of the itemId (location handling, selection info)
- One needs pluggable mechanisms to map these representations together:
...
Overview
Content Tools