Support us on Patreon
PayPalThe Xfce desktop environment is expanding with plans afoot for a new Wayland compositor called xfwl4.
In an official blog post the team announced that using donations from the community, they're going to fund Xfce core developer Brian Tarricone to create xfwl4, a brand-new Wayland compositor for Xfce. It will use up a "significant portion" of their funding but they "believe it’s an important investment in Xfce’s future". Makes sense, considering more distributions have begun dropping support for X11.
Written in Rust, their goal for xfwl4 is to offer the same functionality as xfwm4 as much as possible, but it will be a rewrite and not be based on xfwm4.
Why are they doing a rewrite? As they explained in the post:
The first attempt at creating an Xfce Wayland compositor involved modifying the existing xfwm4 code to support both X11 and Wayland in parallel. However, this approach turned out to be the wrong path forward for several reasons:
- Xfwm4 is architected in a way that makes it very difficult to put the window management behavior behind generic interfaces that don't include X11 specifics.
- Refactoring Xfwm4 is risky, since it might introduce new bugs to X11. Having two parallel code bases will allow for rapid development and experimentation with the Wayland compositor, with zero risk to break xfwm4.
- Some X11 window management concepts just aren't available or supported by Wayland protocols at this time, and dealing with those differences can be difficult in an X11-first code base.
- Using the existing codebase would require us to use C and wlroots, even if a better alternative is available.
Pictured - Xfce on Linux Mint 22.3
As part of it they want to add support for xdg-session-management and XWayland and work has already started on the xfwl4 project. With a first development release hopefully coming around the middle of the year.
Brian has already started work on the project, so stay tuned for the first development release of xfwl4, which we hope to share around mid-year.
See more on the official Xfce website.
Article taken from GamingOnLinux.com.
See more from me
You can also find comments for this article on social media: 
Okay, now for real: that's a great change. Finally XFCE will start to catch up.
Mr. Pinsky 7 hours ago
Quoting: SzkodnixOkay, now for real: that's a great change. Finally XFCE will start to catch up.Switching WM in Xfce is fairly easy, but it is interesting how LXQt got Wayland support before Xfce.
Dana Souly 6 hours ago
walther von stolzing 5 hours ago
Quoting: tmtvlThat's because lxqt is using labwc as its WM. So could Xfce; but apparently wlroots being written in C disqualifies it.Quoting: SzkodnixOkay, now for real: that's a great change. Finally XFCE will start to catch up.Switching WM in Xfce is fairly easy, but it is interesting how LXQt got Wayland support before Xfce.
If this announcement contained some specifics as to what the Xfce devs find lacking in wlroots, and how they aim to remedy that, I think I would've been more enthusiastic. E.g. bare wlroots/labwc (as opposed to sway that comes with its own IPC interface) is still waiting on various wayland extensions to gain important features -- such as exposing to the user which window goes in which virtual desktop (?!).
'Wayland support' isn't a magical on/off switch. Various components of the Xfce environment already got 'wayland support' by virtue of the GTK3 port several years ago. The panel became usable on wlroots compositors as of 4.20, albeit with missing plugins -- most notably the virtual desktop pager, due to the missing extension I was talking about above.
If Xfce devs were to adopt labwc or wayfire are their WM, and then contribute to wayland protocols development to bring those WMs to feature parity with xfwm, they would've benefitted a wider array of desktop environments. Apparently that's an unreasonable ask.
Quoting: amataiShouldn't we call it WFCE then ?No, because the X in Xfce doesn't stand for X11. Or anything else. It's just a name that looks a lot like an acronym, for historical reasons.
How to setup OpenMW for modern Morrowind on Linux / SteamOS and Steam Deck
How to install Hollow Knight: Silksong mods on Linux, SteamOS and Steam Deck