Javier Collado | 4 Aug 10:27 2009
Schmitter, Marc - SFMH | 10 Aug 21:10 2009
Kees-Jan Dijkzeul | 11 Aug 08:20 2009
Ray Satiro | 11 Aug 05:01 2009
Ray Satiro | 11 Aug 13:44 2009
Javier Collado | 11 Aug 15:13 2009
Joe Wells | 14 Aug 09:39 2009
Joe Wells | 14 Aug 09:43 2009
Kees-Jan Dijkzeul | 15 Aug 10:51 2009

Re: Inactivity timeout configuration

I guess you hit the nail on its head:

Workrave is designed for controlling the time spent typing.

If you are trying to solve any other problem than that, one needs to
wonder if
1. The problem can really be solved
2. It would be a meaningful extension to workrave

As to point 1, I guess experience shows that the answer is "no", and not
for lack of trying. The fundamental problem is that workrave cannot read
your mind and hence cannot know that you are using the computer, unless
you are typing and/or using the mouse. Of course you can make some
educated guesses, by fidding with activity timeouts, or assuming the
user is always using the computer ("Suspend timers when inactive",
anyone?) At one point I even proposed adding webcam support to workrave,
such that workrave can "see" you using the computer. The point is that
all of these educated guesses are bound to be wrong for someone, and
hence require extensive UI support to configure, which brings me to point 2.

Workrave tries to adhere to the unix design goal to "do one thing, and
do it well", as well as to have the right defaults, instead of adding
configuration (Gnome's "less is more" philosophy). I am pretty happy
with where we are in that respect. If your problem is "controlling the
time spent typing", there is no tool I'd recommend over workrave (and
believe me, I've looked), even though configuration is a bit complex

Of course, elements of workrave could be reused to solve other problems
as well. Workrave has really nice break windows. If only we could
(Continue reading)