feat: add swaync wallbash support (alpha)

[Jax-Tsai-zero]

wallbash support for swaync, tested.

(alpha version and still optimizing)

[kRHYME7]

Cool.

I have been using swaync for months now. Swaync works pretty well except for the GTK bug.

[Jax-Tsai-zero]

I use swaync for a long time too.
Actually I'm on waybar rework branch for a long time.

What do you mean gtk bug. Seems like I've never seen it?🤔

[kRHYME7]

I'll compile a screenshot later.

[kRHYME7]

BTW how was the waybar rework?

Should we make a dev branch and make a channel for dev Branch in discord?

This way it is unlikely to break the master Branch.

We needed testers in the dev branch who are able to test changes.

[kRHYME7]

This

And the on GTK bug when css uses gtk isntead of custom

[Jax-Tsai-zero]

Waybar rework is great 👍

I agree with you. I think it's stable enough to be test. 😂

[Jax-Tsai-zero]

Imo Maybe the gtk bug is because there's some css feature it doesn't support. I'm working on a standalone config and css, so it's ok for general usage.

[Jax-Tsai-zero]

Oh btw the new waybar rework doesn't recognize the old font setting in hyde.conf, I need to manually configure in waybar user config file (css if I don't get it wrong).

---

Edit:

Another problem is, when I have so many windows open, the right part just squeezed out of the screen🤣

Idk if we can fix it by scripts, or only by upstream.

[kRHYME7]

Try to reload all

swaync-client -R && swaync-client -rs

[kRHYME7]

$HOME/.config/swaync/theme.css | hyprctl dispatch -q exec -- "swaync-client -R && swaync-client -rs"
/* Import wallbash */
@import "<<HOME>>/.cache/hyde/wallbash/gtk.css";

/*
*
* control center
*
* */
/* background */
@define-color sw-cc-bg #<wallbash_pry1>;
/* border */
@define-color sw-cc-border-bg #<wallbash_pry4>;

/*
*
* notification title 'the notification word on control center'
*
* */
/* foreground */
@define-color sw-noti-titl-fg #<wallbash_pry3>;
/* shadow */
@define-color sw-noti-titl-shad #<wallbash_pry4>;

/*
*
* notification window
*
* */
/* background */
@define-color sw-noti-window-bg #<wallbash_pry1>;
/* border */
@define-color sw-noti-window-br #<wallbash_pry4>;
/* color */
@define-color sw-noti-window-txt #<wallbash_txt2>;
/* hover */
@define-color sw-noti-bg-hover #<wallbash_pry2>;

/*
*
* summary message
*
* */
/* foreground */
@define-color sw-msg-sum-fg #<wallbash_pry3>;
/* shadow */
@define-color sw-msg-sum-shad #<wallbash_pry4>;
/* time */
@define-color sw-msg-time #<wallbash_pry4>;
/* body */
@define-color sw-msg-body #<wallbash_pry4>;

/*
*
* notification group
*
* */
/* icon */
@define-color sw-noti-gr-icon #<wallbash_pry4>;
/* button */
@define-color sw-noti-gr-collapse-but-hvr #<wallbash_pry4>;
/* icon */
@define-color sw-noti-gr-collapse-but-icon #<wallbash_pry4>;
/* button */
@define-color sw-noti-gr-close-btn-hvr #<wallbash_pry4>;
/* icon */
@define-color sw-noti-gr-close-btn-icon #<wallbash_pry4>;

/*
*
* clear all button
*
* */
/* background */
@define-color sw-clr-btn-bg #<wallbash_pry3>;
/* foreground */
@define-color sw-clr-btn-fg #<wallbash_pry4>;
/* border */
@define-color sw-clr-btn-br #<wallbash_pry4>;
/* background */
@define-color sw-clr-btn-hvr-bg #<wallbash_pry2>;
/* foreground */
@define-color sw-clr-btn-hvr-fg #<wallbash_pry4>;

/*
*
* DND 'don't disturb
*
* */
/* foreground */
@define-color sw-dnd-fg #<wallbash_pry4>;
/* shadow */
@define-color sw-dnd-shad #<wallbash_4xa1>;
/* background */
@define-color sw-dnd-btn-bg #<wallbash_pry3>;
/* border */
@define-color sw-dnd-btn-br #<wallbash_pry4>;
/* when checked */
@define-color sw-dnd-btn-chk #<wallbash_pry2>;
/* rounded slider */
@define-color sw-dnd-sli-bg #<wallbash_pry4>;

/*
*
* mpris
*
* */
/* foreground */
@define-color sw-mpris-fg #<wallbash_pry4>;
/* background */
@define-color sw-mpris-bg alpha(#<wallbash_pry3>, 0);

/*
*
* Buttons Grid
*
* */
/* background */
@define-color sw-btn-grd-bg alpha(#<wallbash_pry4>, 0.1);
/* foreground */
@define-color sw-btn-grd-fg #<wallbash_pry4>;
/* hover */
@define-color sw-btn-grd-hvr-bg #<wallbash_pry2>;

/*
*
* Volume Widget
*
* */
/* background */
@define-color sw-vol-wid-bg alpha(#<wallbash_pry4>, 0.1);
/* foreground */
@define-color sw-vol-wid-fg #<wallbash_pry4>;

/*
*
* Brightness Widget
*
* */
/* background */
@define-color sw-bright-wid-bg alpha(#<wallbash_pry4>, 0.1);
/* foreground */
@define-color sw-bright-wid-fg #<wallbash_pry4>;

/* NOTE: this is here for testing */
/* @define-color red rgb(247, 83, 65); */

/*
 *  Wallbash colors for tweaking
 * please use ` alpha(#hex, alpha) ` to set the alpha value
 *   to achieve the rgba effect
 */

Try to use this template. swaync has limited elements so I think it's fine to explicitly declare them to be refined further.

Also importing the gtk css so that wallbash colors can be extended further.

[Jax-Tsai-zero]

good idea.

i'll do it.

[Jax-Tsai-zero]

@kRHYME7 I think this can be merged for test now😆

[Jax-Tsai-zero]

hmmm? Anything goes wrong or should I fix something? Or we're not going to support swaync as part of wallbash?🙃

[kRHYME7]

Ops Sorry I accidentally nuke dev branch! I can't reopen PRs because I forgot some of them, including this one.

[Jax-Tsai-zero]

@kRHYME7 Maybe it's good to merge this for testing? Or you have any other awesome idea?🤣

[kRHYME7]

There's an implementation I want for this. Like the waybar implementation. If we started merging this now we might populate unwanted/stray files too early.

as this is following the dev branch you should find someone who could test this. Let's reach out @HyDE-Project/testers

Spoiler alert, dunst is more stable than swaync. This is based on current experience.

I will be testing on this Branch too

[kRHYME7]

@Jax-Tsai-zero please routinely update this branch when the dev branch is updated. Thank you

[Jax-Tsai-zero]

Got it👍👍

[ErikReider]

So the bug mentioned is the users GTK customizations (~/.config/gtk-4.0/gtk.css) overriding the stock swaync CSS values, like the window background, making it gray instead of transparent. The latest version should fix this where the default CSS overrides those changes :)

More info here: ErikReider/SwayNotificationCenter#592

[kRHYME7]

Thank you, @ErikReider

BTW I am very curious if "cssPriority": "application", should output like this ? What adjustments should we do on our side. I honestly preferred using the gtk-theme ever since gtk3 and gtk4 of swaync I still get this problem. "cssPriority": "user", is working as intended though.

manpage

cssPriority
type: string
default: application
values: application, user
description: Which GTK priority to use when loading the default and user
CSS files. Pick "user" to override XDG_CONFIG_HOME/gtk-3.0/gtk.css

swaync 0.12.1-1

[ErikReider]

The "application" level is a lower priority than "user" (which your gtk overrides uses). So if you have anything in your overrides changing the window background color, it will affect swaync, so a user level is needed to override those overrides sadly... nothing that i can do other than provide workarounds

More info here:

• https://docs.gtk.org/gtk3/const.STYLE_PROVIDER_PRIORITY_APPLICATION.html
• https://docs.gtk.org/gtk3/const.STYLE_PROVIDER_PRIORITY_USER.html

[kRHYME7]

The "application" level is a lower priority than "user" (which your gtk overrides uses). So if you have anything in your overrides changing the window background color, it will affect swaync, so a user level is needed to override those overrides sadly... nothing that i can do other than provide workarounds

Noted, basically we should use user, instead of application (based from gtk-theme css) is unpredictable. I'm just curious as to why application is default.

Thank you for dropping by.

[ErikReider]

I'm just curious as to why application is default.

No one really used those overrides with gtk 3 as they weren't needed, so picked the lowest priority for some reason. But now when gtk 4 has removed specifying a theme, people started using it and I deeply regret defaulting to the application priority xD

[kRHYME7]

@Jax-Tsai-zero how about I merge this silently so we can have the files upstream. We will just omit the restore_cfg.psv for now therefore swaync configs will not be available in the installation until ready.
I wanted to work on this slowly.

[Jax-Tsai-zero]

ok, I'll just move back to dunst.

[ErikReider]

Have you tested the latest -git version?

[kRHYME7]

We will omit the restore_cfg.psv for now; therefore, swaync configs will not be available during the installation until they are ready.

To be clear, the configs will be shipped with HyDE, but the installation part will not be available yet.

I have been daily driving swaync for months now without any issues. We have similar configs.

However, I would like to know the status of this feature: ErikReider/SwayNotificationCenter#607. @ErikReider, could you shed some light on whether this is possible?

If it is not possible, we can implement workarounds on our side. But if you have the time to implement this, it would be worth waiting, since the workaround would be a breaking change.