bscreensaver/util/Cargo.toml

[package]
name = "bscreensaver-util"
version = "0.1.0"
edition = "2021"

[lib]

[dependencies]
anyhow = "1"
clap = "3"
env_logger = "0.9"
humantime = "2"
lazy_static = "1"
libc = "0.2"
shell-words = "1"
toml = "0.5"
xcb = "1"
xdg = "2"
zbus = "3"
Initial import. Most things seem working. This includes an abortive attempt to do a gtk4 dialog (which I don't think is possible, as gtk4 doesn't allow embedding toplevels anymore), and an iced dialog, which I just never started writing. 2022-05-04 00:05:06 +00:00			`[package]`
			`name = "bscreensaver-util"`
			`version = "0.1.0"`
			`edition = "2021"`

			`[lib]`

			`[dependencies]`
Add 'New Login' button to unlock dialog 2022-05-04 07:22:00 +00:00			`anyhow = "1"`
Initial import. Most things seem working. This includes an abortive attempt to do a gtk4 dialog (which I don't think is possible, as gtk4 doesn't allow embedding toplevels anymore), and an iced dialog, which I just never started writing. 2022-05-04 00:05:06 +00:00			`clap = "3"`
			`env_logger = "0.9"`
Move config parsing to util crate 2022-05-04 22:37:28 +00:00			`humantime = "2"`
Initial import. Most things seem working. This includes an abortive attempt to do a gtk4 dialog (which I don't think is possible, as gtk4 doesn't allow embedding toplevels anymore), and an iced dialog, which I just never started writing. 2022-05-04 00:05:06 +00:00			`lazy_static = "1"`
			`libc = "0.2"`
Make the new login button stuff more automatic By default it'll look at your environment to try to figure out which display manager is used in order to start a new session. We first try the org.freedesktop.DisplayManager dbus interface, and if that fails, inspect XDG_SESSION_DESKTOP to try to figure out which display manager is running. The user can also still specify the correct display manager, or a custom command. 2022-05-16 03:50:45 +00:00			`shell-words = "1"`
Add 'New Login' button to unlock dialog 2022-05-04 07:22:00 +00:00			`toml = "0.5"`
Don't forward enter or escape to unlock window on first event If the user presses enter or escape in order to get the unlock dialog to show in the first place, forwarding that event to the dialog will only cause it to close immediately. Also took the opportunity to clean up the dependencies where I have my own patches. I'm now using the cargo 'patch' section so that the dependencies specified in the individual Cargo.toml files are clean. 2022-05-18 02:44:38 +00:00			`xcb = "1"`
Add 'New Login' button to unlock dialog 2022-05-04 07:22:00 +00:00			`xdg = "2"`
Update dependencies 2023-09-25 18:34:26 +00:00			`zbus = "3"`