Improvements to pomodoro timer

[almarklein]

The current Pomodoro implementation is rather basic, and still marked experimental. We also got some feedback in the mean time.

Possible improvements:

• If you keep working (or breaking) longer then the designated time, show the extra time worked (and maybe the surplus time).
• Maybe send additional notifications if the Pomo workflow is not continued (the user is stuck working or breaking).
• Make the time slots configurable (as opposed to being hard-coded at 25m and 5m).
• Some sort of visual progress indicator (as opposed to a timer that counts down).
• Make it more visually engaging (colors, etc.)
• Possibility to let Pomoro run when you start a new record. Maybe an auto-start option that can be disabled?
• Ability to skip directly to the next phase, with one button (or key press). E.g. when you're done a bit early, or come back from a break and there is just 1m left.

• 124

• Related to the above: ability to also provide a title.
• Idea: move timer in a separate window/popup for better focus.
• Option to make the pomo tool stop the record when the break starts, and resume when the break ends.

Let me know if you have further suggestions!

[Elarnon]

An additional suggestion: allow to associate pomodoro with specific tags (either opt-in or opt-out --- could be set up similar to tag-specific targets). For instance I typically want to use pomodoro for #code or #writing but not for #meeting or #lunch

[GitHofi]

Hello, I would like to suggest the following small change to the Pomodoro timer:

💡 The suggestion: An option so that the Pomodoro timer does NOT "reset" when a new entry is made in the time line. What should still happen is that the pomodoro timer starts automatically when I create a task in the timeline AND CURRENTLY NO pomodoro timer is running.

This behaviour is currently the only reason for me not to use the pomodoro timer in TimeTagger, although I do work with other pomodoro timers otherwise.

💬 The background for this request: I also work repeatedly on a sequence of small tasks for which I make different entries in the timeline. For example, when I take 60 minutes to answer my emails, but they deal with completely different topics. Now I would like to work through the entire session in which I am working on the emails using Pomodoros. But if there is a new task entry in the timeline every few minutes, the Pomodoro timer is currently reset each time → so I can't use it in such situations.

💡💡 Additional idea (but probably more time-consuming): If you want to put some more effort into the feature right away or as an Idea for later.... You could also automate the situation described above using clever logic. It would then have to work in such a way that when a new task is created in the timeline and the pomodoro timer is running, it is checked whether at least one pomodoro time period has already passed for the previous task (or in other words, whether the previous task took more than 25 minutes). If it was shorter than 25 minutes, the current pomodoro time is left running; if it was longer than 25 minutes, a new pomodoro session is started.

But perhaps this logic described is not as simple as it seems or leads to other complications. Therefore, for the time being, I have suggested the very simple option in the settings → simply do not perform a reset when a task is entered.

I hope I have described the idea well. Thanks for TimeTagger - I use it every day 👍

Kind regards Chris

[almarklein]

Thanks for the suggestions!