- I had a case where after a short break AFK time out, it gave me
ten minutes until the next short break.
- This is actually the correct behavior I think, because the time to the next long break was just over 20 minutes. See the following log to see what I'm talking about:
7:33:36 PM - Welcome to the Gentle Break Reminder!
7:33:36 PM - Next break (short): 7:50:02 PM
7:33:36 PM - Next long break: 8:23:35 PM
8:03:23 PM - Away from the computer enough to reset the short break.
8:03:26 PM - Next break (short): 8:13:21 PM
8:03:26 PM - Next long break: 8:23:35 PM
- Show a tool tip over the glow box which indicates which break this is for. Make this optional. (From Matt.)
- Set up proper file logging and log rotations. Preferably the file
logs would be in JSON format, so they could easily be read with
cutelogor maybe Grafana or something similar. - Make the program run on start-up/login.
- Show a intro wizard on first run. Introduce the glow box and allow moving it to wherever the user would like. (Introducing the glow box is an idea from Matt.)
- Add an about entry to the system tray icon.
- Add a splash screen.
- Make this optional in the config.
- Show the time to the next break in the tool tip for the task bar
icon. (Also mentioned by Brenden.)
- Allow configuring which type of time is shown in the tool tip, the absolute time, the relative time, or both (or even possilby neither).
- Monitor keyboard and mouse activity to reset breaks after a certain amount of time.
- Add a tool tip/title to the task bar icon.
- Allow setting parameters through a configuration file.
- Set the window title of the break screen, so it doesn't show up as
gentle.pyor whatever it shows as. - When the "about" window is closed using the window decoration close button, it exits the entire program. It should just close the "about" window.
- The countdown timer glitches/shows the wrong value when the long break screen is shown.
- Remove the context menus from the glow box, or at least the nonsensical entries (for now).
- Move issue tracking over to a proper issue tracker.
- Package into an installer.
- More linting.
- Set up a website for this thing.
- Refactor functions to be shorter.
- Include an actual bell.
- Make things that should depend on the config file actually depend on the config file, instead of being hard-coded.
- Change 'regular' to 'long' in the config files (for consistency).
- Change console logging to only print information relevant to the end user.
- Create a GitHub repository for the project.
- Include the
stamalibrary. - Get a proper icon.
- Add documentation on how to install the project.
- Change the long break color to violet, and the short break to blue.
- Stop logger from spewing debug stuff. I need to reduce this further in the future, and use proper file logging with rotation in the future.
- Code formatting.
- Linting.
- Secret, secret! I've got a secret!
- Allow taking a short break or long break from the task bar icon.
- Allow skipping a break from the context menu of glow box.
- Internationalization.
- If you are late to taking a regular break, allow the option of extending the break length up to a certain amount.
- Add a command line option to allow the user to specify which level of logging to show in the terminal.
- Add a progress bar to the break screens.
- Make the text font size of items on the break screen adjust automatically to fill the space that they exist in. I've got a Python script in my extras folder where I was experimenting with this, but set it aside in the interest of time, so I shouldn't have to start completely from scratch.
- Change the color/icon of the taskbar icon depending on if the user is AFK or in limbo.
- Add a reminder to drink water a certain (configurable) amount of time before a long break. (I find my self drinking water during a long break and then taking a "forced" break before the next long break. It would be nice if these "forced breaks would roughly correspond with the scheduled long breaks.)
- Show time stamps with AFK events that are printed to the console. I.e. "You've been away from the computer since 12:34:56, long enough ... blah blah blah".
- Track how long on average it takes the user to click on a long break notification, and then allow the option of automatically setting the early notification to show up that amount of time before the long break is due. You could do this for the short break as well, but I don't know if it would make as much of a difference. I'll often delay taking a long break until after I've gotten to a good stopping point, which sometimes can be several minutes.
- Make the splash screen not show up if the program is started on log in.
- Allow setting the opacity of the glowbox.
- Allow setting times with a time format, i.e. "50m" or "T0:50:00" or something similar.
- Add a notification sound to indicate when the break is done.
- Show a skip break button on the short break screen. (From Matt.) Make this optional, possibly with the default to off.
- There is no indication to the user of how long the short break lasts. --> Add the short break time to the short break screen.
- There is no description of what is going on on the long break screen, only a countdown timer. --> Provide information to the user on what is happening. ("Get away from the computer and stretch your legs for a bit. 6½ minutes remaining.")
- When you click the long break early notification glow box, and then click the "skip break" button, it goes right back to showing the glow box. It should instead go to waiting for a short break. --> I think the issue is that the program compares the current time with the clock time set for the next notification. Since the next long break isn't past due when you click the notification early and then skip the break immediately, it thinks the next thing it needs to do is wait for the next break, which is imminent and already in the early notification period.
- Create a visual demo of what the application does in the README.
- Properly update the
piprequirements.txt.- I also need to figure out how to test this program against all supported versions of Python. It would be nice to automate something like this, but that's not something I'm knowledgeable of right now.
- Set up automatic builds whenever a commit is tagged as a release.
- Track when a user is at the screen so I can compute the percentage of time (over the last 'x' hours) that they been in front of the computer.
- Send a ntfy notification, so when you are wandering around on your phone you know when your break is done.
- Figure out if a window has focus, or if this is even an possible to do with QT/PySide. If a break window looses focus, either pause it or count it as finished (depending on if the break is in-progress or finished).
- Round the corners on the glow box rectangle.
- Make the glow box optionally resizable from all four corners.
- Allow dimming the screen during breaks.
- I've noticed in testing that the long break will occasionally be pushed back. --> I believe that this is because if the short break is taken late and then ends after the long break is due, it sees that the long break is past due and resets its next time. I need to address this, possibly by only updating the next scheduled long break on long break finished and in-progress exit. I think I also need to create a timeout event on the late notification for the short break that will transition to a long break late notification (or maybe a long break early notification) if the long break is becoming due.