Draft
Conversation
Contributor
|
Haven't looked at the implementation yet, but from the description, if #121 were to be figured out and panel widgets were implemented as plugins, we would have access to quite a lot of functionality, and, in turn, all (bar the authentication) that is written for the lockscreen first could serve for the panel, no ? |
- Delay and Retry claiming finger print reader on failure - Remove saving and using of name of fingerprint to request as we weren't using it anyway - Added volume mute & mic mute plugin
Collaborator
Author
|
I'm leaning heavily on existing panel widget code, but the factoring isn't similar enough to be able to use them 1:1. |
Add weather plugin
- Added '--now' and '-n' to lock instantly without fade-in
weather: Use wf-json instead of yyjson
weather: Update default css
weather: Update weather-fetch.py script
- Allow some widgets to remain through inactivity - MPRIS widget re-appears on track change - Allow each app to add extra Gtk application flags.
weather: Fix icon broken by refactor
- Implemented fingerprint images and styling - Implemented auth fail lockout - Removed PIN submit button - Fixed fade-in, again - Simplified flow of fingerprint reader - Reduced timeouts in fingerprint reader - MPRIS updates play/pause icons depending on state - MPRIS hides self again on stop
- wf-background writes to user temporary cache when background image changes - locker picks up background image changes and matches - recrustify - wf-background inhibit output is now a user option
- add VPN to panel network
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
GTK4 Lockscreen using session ext1.
Has a plugin-styled structure (but all plugins are compiled with it currently, and no external loading is done)
Plugins are individually togglable.
Plugins that can unlock the screen are:
Costmetic and functional plugins:
TODO Plugins:
Other notes:
Enabling PIN unlock requires creating a hash file:
Use the GTK app
wf-locker-pinto set or change PIN, or manually on terminal withecho -n "1234" | sha512sum | head -c 128 > ~/.config/wf-locker.hashObviously replacing the numbers quoted in the echo. Any number of digits between (inclusively) 1 and 20 is accepted. Writing non-digits into this will make it impossible to auth with PIN.
Fingerprint reader must have an enrolled finger to enable. It will also only accept the first one in the list of presented options.
Password has no 'submit' button as it is assumed the user has an enter/return at that point.
It is possible for user to choose which part of the lockscreen a plugin displays in, but not the order of items. If you put all plugins into center-center of lockscreen then the plugins are shown top-to-bottom in alphabetical order. One option would be to sort the keys before we iterate on them in
on_monitor_present.Weather has a bundled helper script and instructions to set up. Without these it will hide itself from view.
Exit Codes:
exit(0) : The locker started, showed a lockscreen & passed pre-wake dimming. The lockscreen is now fully in effect
exit(1): The process waited a minute, without being told the lockscreen has finished. Considered an error
exit(2): The program crashed or was interrupted before it finished locking.