||1 year ago|
|data||1 year ago|
|docs||3 years ago|
|po||3 years ago|
|screenshot||3 years ago|
|script||3 years ago|
|src||3 years ago|
|.gitignore||3 years ago|
|LICENSE||3 years ago|
|README.md||2 years ago|
|meson.build||1 year ago|
|meson_options.txt||3 years ago|
To build TUF Manager the following is needed:
This software will only work if using the hackbnw/faustus driver module.
Build TUF Manager's vala documentation.
Build external valadocs that TUF Manager utilizes and calls.
Build the cli interface.
Build the gui interface.
Build the tray icon
Authentication is not required to use the TUF Server that runs in the background as a daemon, if this is set to false polkit is used for authentication. Setting this to false is more secure, but also makes things like auto restore of settings on login impossible to do without a password.
There are 3 programs and 1 daemon supplied by TUF Manager.
This allows controlling the TUF laptop functions via command line interface.
This supplies a graphical interface to control the TUF laptop.
This is the daemon that runs in the background and handles all requests from both tuf-cli and tuf-gui.
This is the tray icon to control the TUF Manager program. It should automatically start in any desktop environment that supports xdg.
The restore settings option saves the changes made on a per user basis. This means that for example if a different user logs in and the tray icon is running, it will restore their settings. So for example user A can have a blue keyboard and user B can have a green keyboard. Or even change keyboard colors based on the distro that is booted. For example when in linux mint a green keyboard and when in fedora a blue keyboard.
The other important use of the restore settings options is the fan mode. Normally fan mode does not survive a reboot. It is always set to "balanced" when booted. However now when the user logs in it restores the previous fan mode that was saved.