Lab Wayland Compositor 0.8 Released, Ported To wlroots 0.18

[phoronix]

Phoronix: Lab Wayland Compositor 0.8 Released, Ported To wlroots 0.18

Lab Wayland Compositor "labwc" v0.8 is now available as the newest release of this Wayland compositor that has been re-based against the wlroots 0.18 Wayland library...

https://www.phoronix.com/news/Labwc-Lab-Wayland-Compositor-08

[Gabbb]

This is where floating Wayland is at, bar none. Labwc seriously needs more attention. They recently implemented box resize, it's such a simple thing, but it helps tremendously with some laggy xwayland windows & FF.

[pWe00Iri3e7Z9lHOX2Qx]

Thanks for the article / reminder. This is one of the projects I definitely want to check out.

[faugus]

This is such a good project. It really needs more attention.

[reba]

Yay! As you all know I'm a happy camper with labwc for a longish time already.

Once I built it directly from git when it was fast moving; now it has calmed down and I switched over to installing from arch (CachyOS) repos as it's so stable nowadays and the functionality is fully there so I don't need a fast pace anymore.

The option to build labwc without any X support/Xwayland is possible when building from git and it works reliably, but I don't mind the extra deprecation compatibility layer but also won't mind if they remove any X remnants altogether.

tl;dr: Great project, great devs, big kudos!

[fallingcats]

This is where floating Wayland is at, bar none. Labwc seriously needs more attention. They recently implemented box resize, it's such a simple thing, but it helps tremendously with some laggy xwayland windows & FF.

What you mean by that exactly? I haven't noticed much lagging when resizing firefox on kde (aside from window repainting being slow), how would labwc be better?

[skeevy420]

Once I built it directly from git when it was fast moving; now it has calmed down and I switched over to installing from arch

Now that's pretty funny

[Gabbb]

What you mean by that exactly? I haven't noticed much lagging when resizing firefox on kde (aside from window repainting being slow), how would labwc be better?

If your computer is a nuclear reactor while using a 125hz office mouse/trackpad, then it doesn't matter, I suppose. On a laptop it would be good for conserving battery even then.

Box resize helps, because the window is only redrawn after the resizing/moving operation is complete, instead of constantly redrawing. (god help you with a 1000hz gaming mouse, while using an ancient intel igpu)

[fallingcats]

If your computer is a nuclear reactor while using a 125hz office mouse/trackpad, then it doesn't matter, I suppose. On a laptop it would be good for conserving battery even then.

Box resize helps, because the window is only redrawn after the resizing/moving operation is complete, instead of constantly redrawing. (god help you with a 1000hz gaming mouse, while using an ancient intel igpu)

Okay, I understand. Seems like it should be very useful during vnc/rdp connections. But for basic desktop tasks, even my 12yo laptop doesn't really struggle with resizing windows all too much. I guess ymmv

[Quackdoc]

IMO Compositors really should be vendoring and statically linking their backends unless they don't expect anyone else to use them. the mismatch makes having packages co-exist a massive pain. It's really nice that labwc does this. Arch gets around this by simply packaging wlroots and wlroots0.17, but that's not great. gamescope can vendor wlroots which is nice, but it on arch it relies on libdisplayinfo package which breaks shit anyways.