A few days ago i made a post on various platforms sharing my software ScreenGuard which received mixed reviews every where , since I AM using it for myself i decided to take in the reviews and am working towards adding necessary features and primarily polishing up things that were left behind and can have some 1st time setup hiccups.
The new features-
* Settings menu added
General tab(control notifications and sounds)
- add notification sounds(custom options too)
-toggle sounds and notifications for various causes
- dark mode(asked bby a few people so added the option)
Tracker Daemon tab
-stop background daemon
- toggle autostart of daemon on boot
- warning when daemon is off Pomodoro timer tab
- Turn on pomodoro in focus mode settings (fixes the unbaked settings of focus mode in v0.1.0 -set break between pomodoros
- no of pomodoro loops
* Daily limits can now be set instead of the fixed 8hr daily limit bug with v0.1.0
* Several changes to Daemon, including some minute layout changes to optimise resources while adding the newer features which are Stated above
Note: this is a beta release and will NOT be pushed to the APT ,COPR AND ARCH repositories for casual users, this is meant for testers and people eager to help me out find the bugs and tiny issues here and there AND YOU CAN HAVE A LOOK INTO THE CODE IN THE BETA BRANCH OF THE REPOSITORY, it hasn’t been pushed to main branch to keep it clear until bugs are fixed.
Release page: (https://github.com/adityakrishnan005-a11y/ScreenGuard/releases/tag/v0.1.1-beta.4)
_____________________________________________________________________________
CLEAR AI EXTENT
Codebase: Manual
Implementation: Manual
Debugging:Assisted
Packaging: generated(specifically for Custom aarch repository due to issues with AUR)
Documentation: Assisted
And about the common issue u say , will it be maintained regularly? I have had only 11 stars on GITHUB honestly…and yet there u can see 2 new beta releases in the beta branch in a difference of about 7-8 days. This is because it’s a project of personal interest and i WILL have to improve it if I want to use it…there is no substitute to this in the community right now i believe and u must know that as well. Also creating the BETA branch and not pushing beta updates to repository IS the correct approach because these are under testing and i am testing it on my own device and VMS but actual devices with defferent environments will be a better test and hence this request.
Pushing to the repository (custom repository of apt and aur ) means that whenever people run sudo dnf upgrade or sudo apt upgrade they get the beta version installed
NOTE: I HAVE MENTIONED THAT THE UPDATES WILL NOT BE PUSHED TO THE CUSTOM APT AND ARCH AND COPR repositories , but you can always have a look at the codebase, just switch to beta branch , both versions are there