We could provide a node predicate for each action that can be used to filter the nodes on which an action should work.

Question:

• how can each view / widget that uses the context menu specify the node predicates for each action?
  • the specific action is not known since only the context menu retrieves all known actions and adds them to its menu
  • use microservice-approach and cast to desired action? use microservice-interface to provide function to set a node predicate

The problem was that the actions were defined inside the data manager and thus had access to the node tree.
Now the new context menu holds all actions and the data manager only knows the context menu. The actions don't know the data manager anymore and therefore can not access the model of the data manager view (or the model of the new data storage inspectors).

One could provide the context menu and the actions with the data storage inspector model, which only holds the nodes that are valid with the given node predicate. However, this is similar to just providing the node predicate. It will not solve the problem that some actions should work on node-predicate-filtered nodes whereas others should work on the whole data storage.

Different node levels:

• all data nodes (whole data storage)
• only the currently shown data nodes
• node-predicate-filtered nodes with the new data storage inspectors
• only the currently selected nodes