Xfce Wiki

Sub domains
 

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
releng:wayland_roadmap [2026/08/19 08:43] – [Panel Plugins] gaelreleng:wayland_roadmap [2026/11/01 04:49] (current) – minor formatting & grammar improvements kevinbowen
Line 22: Line 22:
 For Xfce 4.22, the stabilization work continues. Reaching X11 feature parity is not yet our target. For Xfce 4.22, the stabilization work continues. Reaching X11 feature parity is not yet our target.
  
-We are now working on our own [[https://gitlab.xfce.org/xfce/xfwl4|Wayland compositor]]. It is under heavy development, somewhat usable but not stable yet. Please see [[/xfwl4_faq|its FAQ]] for further information.+We are now working on [[https://gitlab.xfce.org/xfce/xfwl4|our own Wayland compositor]], ''xfwl4''. It is currently under heavy development, somewhat usable but not stable yet. Please see the [[:xfwl4_faq|xfwl4 FAQ]] for further information.
  
 Check the table in the [[#component specific status]] section for details and labelled issues by group: Check the table in the [[#component specific status]] section for details and labelled issues by group:
Line 35: Line 35:
 ===== Long Term Goals ===== ===== Long Term Goals =====
  
-It is not clear yet which Xfce release will target a complete Xfce Wayland transition (or if such a transition will happen at all).+It is not yet clear which Xfce release will target a complete Xfce Wayland transition (or if such a transition will happen at all).
 Below is a list of larger tasks which would need to be done in some way for such a transition to occur. Below is a list of larger tasks which would need to be done in some way for such a transition to occur.
  
Line 45: Line 45:
     * No xsettings     * No xsettings
   * Use smithay over wlroots and libmutter for our compositor   * Use smithay over wlroots and libmutter for our compositor
-    * keep the possibility to run xfdesktop and xfce4-panel as separate components+    * Keep the possibility to run xfdesktop and xfce4-panel as separate components
     * Prevent dependency on libgnome-desktop     * Prevent dependency on libgnome-desktop
     * xfce4-panel and xfdesktop have been ported to Wayland assuming our compositor will be based on wlroots.     * xfce4-panel and xfdesktop have been ported to Wayland assuming our compositor will be based on wlroots.
-    * We plan to keep xfwm4 as X11-only, for Wayland a brand new compositor called xfwl4 was created.+    * We plan to keep ''xfwm4'' as X11-only, for Wayland a brand new compositor called xfwl4 was created.
   * Keep X11 compatibility for the foreseeable future   * Keep X11 compatibility for the foreseeable future
     * Nvidia support to Wayland is still problematic, one more reason to keep X11 backward compatibility (nouveau driver usually is slower)     * Nvidia support to Wayland is still problematic, one more reason to keep X11 backward compatibility (nouveau driver usually is slower)
     * Wayland compositors which were written from scratch like Weston or sway will never run as a x11 window manager. But others which started as x11 window managers such as kwin or mutter still keep their x11 window management code     * Wayland compositors which were written from scratch like Weston or sway will never run as a x11 window manager. But others which started as x11 window managers such as kwin or mutter still keep their x11 window management code
-    * FreeBSD has decent [[https://docs.freebsd.org/en/books/handbook/wayland/|support]] for Wayland, OpenBSD is still [[https://www.openbsd.org/papers/eurobsdcon2023-matthieu-wayland-openbsd.pdf|working on supporting]] Wayland+    * FreeBSD has decent [[https://docs.freebsd.org/en/books/handbook/wayland/|support]] for Wayland,  
 +    * OpenBSD is still [[https://www.openbsd.org/papers/eurobsdcon2023-matthieu-wayland-openbsd.pdf|working on supporting]] Wayland.
     * We will archive this by having both a window manager (xfwm4/X11) and a compositor (xfwl4/wayland)     * We will archive this by having both a window manager (xfwm4/X11) and a compositor (xfwl4/wayland)
  
 +[[|Back to Top]]
 ---- ----
  
Line 106: Line 108:
   * Everything to do with keyboard handling (brightness keys, suspend key, etc.) is not restored, since only the compositor is currently able to manage this.   * Everything to do with keyboard handling (brightness keys, suspend key, etc.) is not restored, since only the compositor is currently able to manage this.
  
 +[[|Back to Top]]
 ---- ----
  
Line 141: Line 144:
 Compositors that don't implement the protocols mentioned above will not be supported. Compositors that don't implement the protocols mentioned above will not be supported.
  
 +[[|Back to Top]]
 ---- ----
  
Line 191: Line 195:
 | xfce4-xkb-plugin | no | Non-portable to Wayland in the near future, shows a placeholder on Wayland for now | | xfce4-xkb-plugin | no | Non-portable to Wayland in the near future, shows a placeholder on Wayland for now |
  
 +[[|Back to Top]]
 ---- ----
  
Line 220: Line 225:
   * [[https://gitlab.xfce.org/xfce/libxfce4ui/-/commit/57410e2dffde5271443809a0dbd0280be262ba47|Check if current display is a wayland display]]   * [[https://gitlab.xfce.org/xfce/libxfce4ui/-/commit/57410e2dffde5271443809a0dbd0280be262ba47|Check if current display is a wayland display]]
   * [[https://alexxcons.github.io/blogpost_15.html|Xfwl4 - The roadmap for a Xfce Wayland Compositor]]   * [[https://alexxcons.github.io/blogpost_15.html|Xfwl4 - The roadmap for a Xfce Wayland Compositor]]
 +
  
 [[|Back to Top]] [[|Back to Top]]
 +----
 +
 +[[:start|Return to Main Xfce Wiki Page]]