Open Chris-May opened 1 year ago
How would you envision the behavior if you'd like to see this as a part of the project?
Hey Chris! Thanks so much for your interest, sorry I didn't notice this issue when you filed it.
The new nexus model ( #36 ) has a notion of a "session", which is a tweakable "period during which you want to be productive", rather than fixed intervals. As explained in #33:
If I return to the keyboard at 10:36, there's a feeling that I've "missed" the current block and I should just sit around and wait for the new one. This is bad because the goal of this app should be to maximize intentional time, and always be helping you to get started (if it's time to get started!). There's no incentive to get back to work when you've missed a given pomodoro.
The way that sessions work is that you are repeatedly prompted to start a pomodoro if one is started, and repeatedly prompted to continue your streak if you recently completed a break. Outside of a session, you can still start an individual pomodoro, but you won't be prompted to either start or continue.
I'm going to leave this open because this still needs to be fully implemented in the UI and all the way through the model in terms of automatically starting and stopping. There are four parts to this, which should perhaps turn this into an umbrella issue:
This project could benefit from the ability to alter the schedule during the day.
Sometimes I need a longer break, prefer to start and end a Pomodoro at different times, or want to end the day earlier than the planned Pomodoros.
I see an issue to cancel the current Pomodoro and start a new one, which can be related to this.
How would you envision the behavior if you'd like to see this as a part of the project?