eww VS awestore

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

Awestore - Rubato implementations often reference Awestore (specifically compatibility with it), which was last week's popular AwesomeWM animation framework until Rubato's tantra was read to the above configurations. Nonetheless, its got better documentation, sort of, and is worth a gander as it may make more sense to you or be more helpful to your purposes.

As far as compositing and animating, Awesome itself is NOT a compositor. You will need a separate compositor like picom for things like shadows, background blur, and true transparency. There are forks of picom that also implement window animations but I have not personally tried them. Simple animations can be implemented in Awesome with libraries like rubato or awestore but it's a fairly manual process of changing a window's x and/or y coordinates on a regular interval.