cardboard VS river

The article at the link you posted is about the Cardboard WM.

Shoutout for Cardboard, an awesome Wayland compositor and a rare example of Scrolling Tiling window management.

https://gitlab.com/cardboardwm/cardboard

You have cardboard which is a freestanding wm based on the functionality of the old paperwm plugin for gnome: https://gitlab.com/cardboardwm/cardboard

Er, on my laptop? It might be more precise to say that I can't find any way to make it use anything else; manpages give me nothing, grepping for "layout" in the source tree gives me nothing (relevant; window layouts show up), and there's an open issue (https://gitlab.com/cardboardwm/cardboard/-/issues/30) asking for it, all of which makes me conclude that it doesn't appear to support doing anything but QWERTY. That said, I said "AFAICT" for a reason; if you can prove me wrong I'll be quite grateful (because, seriously, I would like to use this thing).

They can’t be disabled, but I’ve opened a bug about it: https://gitlab.com/cardboardwm/cardboard/-/issues/27

Would it be possible to use the 'layout generator' functionality to create scrolling workspaces in the style of PaperWM or cardboard? Where rather than tiling the traditional way into the space available on the monitor, windows are tiled next to each other in columns on an essentially infinitely wide workspace and scrolled to bring the focused window onto the monitor.

PaperWM is the original inspiration, but then I acted on the suggestion of one of the developers of cardboard and made a plugin for Wayfire.

Cardboard is hosted on Gitlab at https://gitlab.com/cardboardwm/cardboard

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