optionally allow the default to be productive time and the exception list to be non-productive time
flip the default/exception behavior so that any time is presumed to be productive unless one of the configs (app, keyword) matches, in which case it is unproductive.

2 comments
-
Clark Wilson commented
I did a work around for this. I deleted all my items from my "productive" list and then put the unproductive items in there. Then green is unproductive and red is productive. It works well enough.
-
Simon Celen commented
It might be interesting to be able to define custom timeframes. In addition to having (un)productive, you could have "client work", "design", "coding", etc.