mako VS eww

So, using this github issue as a reference, I'm trying to make a wofi menu that appears when a bluetooth file transmission is sent to my PC from my phone (or any other device for that matter).

I currently use mako for the notifications. When I play Strategy Games (Mouse is all over the place) and a notifcation pops up, the mouse gets stuck on the notification message until I click it.

I use avizo as a volume indicator, mako for notifications generally.

I guess some standard notifications app like https://github.com/emersion/mako doesn't suffice, as it isn't related to a window?

mako is a Wayland notification daemon from one of the principal Sway/wlroots devs, and is currently provided with openSUSEway. It's pretty minimalist, but so are most things in the Sway/wlroots ecosystem.

It's a notification, I use mako: https://github.com/emersion/mako

Notifications: mako

Is there any way to force dbus to use a specific notification daemon? On one of my systems, I run both Plasma and Sway. The latter obviously doesn't have a notification system, so I'm using mako. As far as I can tell, mako automatically launches when a notification is fired, however this causes an issue with Plasma. Plasma seems to be shutting down its own notification daemon in favor of anything else that's running, and I'm not sure if there's a way to prevent it from doing that

I don’t use Thunderbird, but does it support using FreeDesktop notifications e.g. that would work with Mako? Some applications will fall back to their own windows if there’s no notification daemon running.

I'm trying to get the most out of my OS (Arch with X11 and Awesomewm), but I'm stuck with the widgets. I would like to create/use some utilities like an interactive calendar, small TODO list, dropdown menu, etc. but using the awesomewm widgets is too difficult and limiting. I found eww but it seems as difficult as the former widgets.

Reported and closed upstream: https://github.com/elkowar/eww/issues/712

The reason, why eww would not start, is because i compiled it myself with rustup according to the official documentation (https://elkowar.github.io/eww/) and not by the AUR. After installing it with the AUR it workes in Hyprland. So in conclustion: If you wanna use Eww on Hyprland, use the AUR method and not the method on the Docs!

Are you as mystified as me? I'll save you the google search: eww is Elkowars Wacky Widgets a standalone widget system made in Rust that allows you to implement your own, custom widgets in any window manager.

Well actually there is https://elkowar.github.io/eww. I used it to make my config and also looked at other configs.

I'm guessing one could use [eww](https://elkowar.github.io/eww/) to create buttons/widgets. And the buttons could dispatch commands to any of the wallpaper/theme changing applications to actually execute the change.

I'd like to get informations from xmonad on all the currently active workspaces and which one is the current workspace. Possibly I'd like to format that information into a JSON object for better integration with Eww, which I'm using as a status bar.

Hi all, I'm trying to configure a bar with eww (https://github.com/elkowar/eww) and I' stuck getting the workspace widget to work.

No, as far as I know. I personally use eww and toggle a calendar when clicking on a time widget. I'm using the config in this repo