Community
Participate
Working Groups
The GEF4 Cloudio and DOT components currently mix framework classes (API) and end-user tooling in their respective UI modules (DOT.UI does actually not provide framework parts yet, but certain classes could be opened as API, as indicated in bug #476891). This prevents to use framework parts without end-user tooling related menu bindings, view contributions, etc. We should IMHO separate both aspects by introducing respective *.UI.User modules that contain the end-user related functionality (e.g. provide the DotGraphView and the related extension). This pretty much complies to the separation of the documentation into user doc and developer doc that is handled in bug #465227.
An alternative would be to introduce capabilities so that all UI contributions can be disabled. This is probably the better option. It would allow to expose parts of the currently internal functionality (e.g. the parser within DOT) later without restructuring the bundles again.
I introduced capability definitions within Cloudio.UI and DOT.UI that allow to disable all UI contributions. As indicated in comment #1 this should be sufficient to use the framework parts without having to cope with unwanted UI contributions. Resolving thus as fixed in 3.11.0 M5.