Repository navigation
Releases: gsl4295/PicoTimers
Releases · gsl4295/PicoTimers
Release list
v0.4
The fourth revision of my PicoLaunchTimer code has released.
Major changes:
- Created new python script, clock.py, for simple desktop use without launch-related things
- Renamed repository from PicoLaunchTimer to PicoTimers
Minor changes:
- Scrapping unit testing idea
Up next (likely in chronological order):
- Create a script that has you choose between launch.py and clock.py on startup
- Add extra time things in clock.py like day of the week and such
v0.3
The third revision of my PicoLaunchTimer code has released.
Major changes:
- Automatic daylight savings time calculations with the help of timeapi.io
- Simplified error handling for json responses
- Updated readme.md and pin-info.md to show more accurate info
Minor changes:
- Once again "improved" the GUI.
- Scrolling text is also slightly more simplified and better understood by me.
Up next (likely in chronological order):
- Simplified "only-clock" functionality... aka removing the "Launch" from "PicoLaunchTimer"
- More comprehensive error handling for certain json responses
- Unit Testing
v0.2-beta
The second revision of my PicoLaunchTimer code has released.
Major changes:
- Added a "manual mode" that allows the user to specify one countdown, and switch to (and from) it with a button.
- Split the gross main_text_area string into 7 rows, each with its own job on the countdown.
- Split the main json parsing function into two, allowing for a simpler access of those variables.
Minor changes:
- Improved the admittedly nice purple color into an objectively better color: green.
- And if you don't agree, the accent color is now an argument in the visuals function.
Up next (likely in chronological order):
- #4 Scrolling text (which is already an imported library in my code, just need to use it)
- #3 More error handling for bad json responses
- #6 Automatic daylight savings time calculations
- #1 So much testing.
By no means is this the end goal for my timer, but I do love where it's at right now. I'm requiring the full release to be 100% (or at least close to 100%) covered by unit testing. So we might go through a few more pre-releases.
v0.1-alpha
Beta file is stable, changing it to main.py