eww VS Waybar

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

I am currently using uair integrated in to my Waybar running on my sway window manager. I use it similar to the way I use watson (both as a CLI tool with Waybar integrations), so it is a good fit for me.

If I understand https://github.com/Alexays/Waybar/wiki/Configuration correctly, what is to be displayed is defined in a JSON file that can be located in one of the directories mentioned.

GNU calls their extensions "equivalent to" things I'd have suggested trying ($_I or $-l), but I'm not sure if the equivalents are themselves GNU extensions, too. Regardless, reading this Waybar Github issue about %OI, I get the impression there was a regression at some point, in any case on March 27th 2022 someone says it "used to work fine until recently".

hope it helps. source btw: https://github.com/Alexays/Waybar/issues/2177

See this issue. CSS and only new properties in config are reloaded when SIGUSR2 is triggered.

I think this has just been added to waybar (wlr/workspaces) to work in a similar manner to how it is in sway/workspaces. No need for fake empty terminals. Something was merged for wwlr/workspaces in the waybar github. See - https://github.com/Alexays/Waybar/pull/2089.