krohnkite VS river

That's exactly what happens. Bismuth was a fork of Krohnkite. If someone needs Bismuth enough, they will pick it up, fork it or whatever.

I wonder if this PR would help you.

No idea what exactly that shell does but in KDE krohnkite https://github.com/esjeon/krohnkite was pretty popular until it was somehow superseeded by bismuth https://github.com/Bismuth-Forge/bismuth (which forked krohnkite or was inspired by or whatever) and now with Plasma 5.27 there's initial work on a native tiling window manager including a whole new API for people to build upon, and which can be accessed with Meta+T.

You can use Kronkite just fine. Bismuth is a fork of it, and their feature-sets are practically the same.

Kwin tiling script - Krohnkite

Do you know how that differs from https://github.com/esjeon/krohnkite it seems like that is another tiling extension.

I love virtual desktops and Krohnkite; it works infinitely better than windows.

More info on the wiki https://github.com/riverwm/river/wiki

Here is the related github issue

If you can get past some minor wayland related annoyances, river is pretty easy imo, you can write a config in whatever format you want, it just needs to be an executable file, the most common type is a shell script. The actual configuration happens by calling the riverctl program from the file, which from what I've heard is a similar method compared to bspwm.

Coming from awesome you may find river more to your liking than sway.

River crashed everytime I closed Chromium. The developer fixed it in 5 minutes :)

I've written a plugin that implements the river-layout-v3 wayland protocol in Hyprland. This means you can run something like rivertile, river-luatile, rivercarro or kile as a layout provider.

Author here. And yeah, as of 0.6.0 it supports master stack - I just called it stack main. I was in fact inspired by river: https://github.com/riverwm/river. River is really promising but is still in very early development. Sway on the other hand has been around for a long time and I, for now, prefer that stability.

In my very specific case, I'd probably start by taking a look at how animations were previously implemented in river, and then I'd pay careful attention to that transform matrix at the end. I'm not super crazy about the implementation using timers to drive it (versus interpolating where the transform should be across a deadline), but I guess they were going for smoothness.

riverwm wayland compositor