I downloaded the KDE spin after reading that it uses W by default as I wanted to know if appimages would work there. I burnt the .iso to a USB, booted the Live OS, and yes, it does use W by default, so thought I would share my findings here
Now that KDE is supported by Wayland, I may give it a try.
Taiwins is a modern and modular wayland compositor, and it is extensible through lua script. It has a builtin shell and GUI system called twidgets Writing a minimum Wayland client using twidgets would take only 20 lines of code.
Taiwins is the tiling as well as a floating window manager, you can allocate windows on your desktop logicially or based on your needs, drag your windows freely.
- fast and small codebase.
- extensible and easy config through lua.
- builtin shell.
- wayland client system.
- configurable theme.
- multi key-presses bindings like emacs.
- dbus support.
- and more.
$ swappy ** (swappy:28283): CRITICAL **: 13:07:02.049: original image not loaded (swappy:28283): GLib-GObject-CRITICAL **: 13:07:02.061: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
I know, I was aware of that. I normally use i3wm with xfce4-panel. In order to use wayland I am using sway but since the xfce4-panel isn't compatible I used another panel, waybar. I did run into a few things but I am going to continue with it this weekend to see how far I can get my configuration to and see how many of my applications work with wayland.I don't think Xfce supports Wayland yet however that may have changed since I've looked into it.