Bugzilla – Full Text Bug Listing
| Summary: | [activity] support integrating activity monitoring outside of the workbench | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Jed Anderson <jed.anderson> | ||||
| Component: | Mylyn | Assignee: | Mik Kersten <mik.kersten> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P4 | CC: | ekuleshov, litrik_de_roy, mik.kersten, mlists, yuri | ||||
| Version: | 0.4 | Keywords: | helpwanted | ||||
| Target Milestone: | 2.0 M1 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Jed Anderson
As another example, if I am debugging, does Mylar know I am debugging? Some of my test cases require a few minutes of setup before I can actually run my test. Having Mylar keep track of my total elapsed time would allow me to say, "This setup takes too long, I need to automate it," with definitive numbers to back up my decision. That second sentence should be: I'd like to mark some tasks as being active even when the workbench is _not_ active. Thanks for the kind words Jed! I know exactly what you mean and want this too. I've been thinking about it and wonder if we could track whether there is activity in any window that's active, but the problem is that this will require platform-specific extensions (I wonder how Windows Messenger does it?). So we may be forced to do what you suggest and keep two times around. The debugging case might be better though, because we may be able to attach to that shell and figure out if it is active. Another todo: we need to exclude time that the task has been paused. Actually for starters I would suggest something more simple. When activating a task get the system time and record it somewhere (task list) When pausing a task get the system time again and record the time spent on the task. Same applies to eclipse shutdown etc... This way you get intervals of time spend in a task which you simply have to add up to get the overall time. No need to track anything outside of eclipse. This won't be as accurate and the user has to remember to pause the task when he is leaving eclipse to do something totaly unnessecary. Stefan: I agree that this is probably the best way to get some of this functionality without getting onto the slippery slope of monitoring OS-specific interaction (which I briefly investigated). However, I am concerned that it would be way too easy to leave such a timer running, so this may require a separate "manual timer" attribute which could be edited directly if needed. Marking helpwanted, at least for now, since we too many other high priority items ahead of this. I also need this because elapsed time shown on Task Activity view is screwed real bad. You can make timer suggested by Stefan more visible by adding icon to the system tray. http://www.eclipsezone.com/eclipse/forums/t66093.html This requires OS-specific monitoring extensions, which are outside of the scope of Mylar. However, what we can do for Mylar 2.0 is enable OS-specific monitoring extensions to contribute to the activity mechanism. Done. Extension point is in org.eclipse.mylar.monitor.ui. Name might still change. Marking fixed. Created attachment 58465 [details]
mylar/context/zip
|