Skip to content
This repository has been archived by the owner on Dec 17, 2021. It is now read-only.

stop and void pomodoro #2

Open
fain182 opened this issue Mar 1, 2011 · 3 comments
Open

stop and void pomodoro #2

fain182 opened this issue Mar 1, 2011 · 3 comments

Comments

@fain182
Copy link

fain182 commented Mar 1, 2011

Sometimes is useful to stop a pomodoro because you have been interrupted, and this should be shown as void in the timer history.

If you start a pomodoro before the previous is finished, the previous should be marked as void in the history.

@mrmemes-eth
Copy link
Owner

Hrmm... how would you feel about just adding a way to delete the current timer. If you delete it, then it's just not shown in the timer history? In a similar vein: would a Pause button work for you?

@fain182
Copy link
Author

fain182 commented Mar 9, 2011

yes, a "delete current timer" could be a simple solution.

A pause button is not contemplated in the pomodoro technique, but maybe can be occasionally useful.

@sukima
Copy link

sukima commented Jun 16, 2011

If I understand the pomodoro technique correctly stopping a pomodoro is effectively voiding it. To represent this in the current version of the tomatoi.st you would just click short break then start a new one. Perhaps I have not fully understood. I think having the length of each timer in the history would be more useful then the last time it was initiated. I will consider forking the source for that.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants