--On Friday, November 05, 2004 2:01 PM -0500 Lorin Hochstein <[EMAIL PROTECTED]> wrote:
Hi Philip,
If a developer was viewing files in Emacs, but was not modifying those files at all, would this show up in "Active Time" calculations? More specifically, what are considered "events" by the sensors?
Lorin
Hi Lorin,
There are two questions here:
1. Active Time is an interpretation of the raw sensor event data stream that indicates the amount of time the user spent actively modifying files. Active time is generated by looking for a single type of Activity event, called the "statechange" event, which is generated by IDE sensors when the user modifies a file during a given interval of time (typically 30 seconds).
2. While all IDE sensors by convention will emit "statechange" Activity events in the same way in order to support the Active Time abstraction, they are free to generate other events for other purposes. There is no limit or constraint on what other types of Activity events an IDE sensor might decide to emit.
One could imagine a 'Busy' abstraction, which would represent the time interval during which any IDE event was detected indicating the user was doing something. The Jupiter code review sensor and associated Review Time analyses implement something similar to this, since during a review it is common for a user to spend significant time reading the contents of a file without editing it in any way.
Cheers, Philip
