...

The actionbar and the statusbar must be synchronized to the selection of the workbench.

Container

We change the containers to identify the items within it not using their paths but instead in a format consisting of the node's identifier and the name of the property if it represents a property. We don't add a dedicated object for this, instead we use a string representation, to keep the memory footprint down.

Actions

The workbench passes on the selected item to the action, if nothing is selected the passed on item is the node used as root for workbench (configured in WorkbenchDefinition.path).

...

Also, the actionbar and the statusbar must be updated based on the new selection.

Events

We're using events to synchronize the workbench after an action is executed. We will need to review the events, when they're sent, if they carry enough detail, and which bus they're sent on.

• to be defined how the look like (source & target?) -> e.g. check how JR does it, reuse?

• should fire uuid - also ensure consistency

• only use id’s?

• add new asset

• Which bus should be informed by content changing actions etc...
  

Moving in Tree (via drag & drop and via actions)

......

Out of scope for this concept

...