Community
Participate
Working Groups
The user activity monitoring that determines whether a user is active is used for time tracking. It is also used by other components, e.g. to suspend Task List synchronizations if a user is not using the machine, and has other potential applications. To improve reuse I propose that we move the activity monitoring extension point and related implementation from o.e.m.monitor.ui to a separate o.e.m.commons.activity.ui bundle. Everything related to interactions events, i.e. interpretation of actual events rather than simple monitoring of any kind of activity would remain in the o.e.monitor component.
I have created separate bundles for the activity monitor. These are the pending changes to consume the new bundles (they are currently not included in the distribution): http://review.mylyn.org/#change,78 http://review.mylyn.org/#change,79 http://review.mylyn.org/#change,80 Shawn, can you take a look at the o.e.m.commons.activity.ui bundle and let me know what you think? The new extension point will replace the activity monitor extension point in o.e.m.monitor.ui which is no longer used (once all pending changes are applied).
The latest iteration is here: https://git.eclipse.org/r/#/c/5983/.
org.eclipse.mylyn.commons.activity.ui, .tests, and - feature are not used. We should either complete this refactoring or delete the bundles if the refactoring is not relevant anymore.
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
