Community
Participate
Working Groups
Monitor UI should provide a generic facility for processing interaction events and not not have a direct dependency on context.core.
I believe it's important to make the proposed change to properly decouple the components and improve reuse but this would require a number of refactorings in the way interaction events are monitored and processed. Furthermore, we should rethink on which level of abstraction interaction monitoring takes place and how events are processed. Currently, it is not well defined which monitors gets instantiated and hence what information is available to consumers of events. While the changes are important, we do not have a strong enough driver to proceed at this point. I'll leave this open for future consideration.
To expand on this furhter, we are missing a split between interaction monitoring, structure bridges and UI tooling. Currently bridges aggregate all three components into one (.ui) bundle. For better reuse we should consider splitting bridge bundles according to their concern and consumers.
Decoupling monitor.ui from context.core is now tracked on bug 360300. I'll leave this bug open for discussion about the interaction event api.
Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn
