6 ms·

What's LXQt's Wayland story?

by genpfault 5y ago

abrowne 5y ago
I'd guess Kwin.
- yissp 5y ago
  Is Kwin usable without plasmashell / the rest of KDE? I always thought they were pretty tightly integrated. I feel we're currently missing a minimalist stacking Wayland compositor in the vein of something like openbox.
  - approxim8ion 5y ago
    KWin is indeed usable without the rest of KDE. It can be used as the window manager for XFCE or MATE, for example. Also, I'm not very educated in this matter, but isn't wlroots a fairly good Wayland compositor? Considering sway is built on it and supports both tiling and stacking, I think that might be worth a look.
    - pantalaimon 5y ago
      > It can be used as the window manager for XFCE or MATE, for example. But that's on X11 then, right?
      - approxim8ion 5y ago
        Yes, although KWin now supports Wayland quite a bit. There's an explanation here: https://community.kde.org/KWin/Wayland#Why_Plasma_needs_Wayland.3F https://community.kde.org/KWin/Wayland#Why_Plasma_needs_Wayl...
    - yissp 5y ago
      As I understand it, wlroots is more of a library that you can build a Wayland compositor on top of (sway being one example). It's not a compositor in and of itself. It still might be a good choice for LXQt if they do plan on supporting Wayland, though.
      - abrowne 5y ago
        One wlroots possibility would be Wayfire https://wayfire.org/ https://wayfire.org/
  - ognarb 5y ago
    It's usable and some people in the automobile industry are interested in using it in an embedded context.
saxonww 5y ago
https://github.com/lxqt/lxqt/issues/10 https://github.com/lxqt/lxqt/issues/10
piaste 5y ago
Some sort of bring-your-own-compositor adventure at the moment, if I'm reading this issue correctly [0]. The thread did mention PaperDE [1] however , which you might want to look at if you're interested in a lightweight Wayland + QT environment. [0] https://github.com/lxqt/lxqt/issues/10 https://github.com/lxqt/lxqt/issues/10 [1] https://gitlab.com/cubocore/paper/paperde https://gitlab.com/cubocore/paper/paperde
akdor1154 5y ago
Tangent... There seem to be a fair few smaller (in community) DE projects (LXQt, XFCE, Cinnamon, Budgie, more I don't immediately recall) who are keen for Wayland support in principal but don't want to be landed with writing/maintaining their own display server. I know there are libs like wlroots, libweston, mir, but in practice it still seems to be too much to bite off to write a display server with one of these. Is there appetite in the Linux desktop dev community for a grab-and-go toolkit-agnostic Wayland display server that allowed DEs to plug in their own independent WM, decorations, animations, shell? In theory shell is doable already by xdg-shell, but splitting WM and decorations out would be a new approach for Wayland. Is this technically feasible? I have the urge to start writing one myself but I'm not experienced in this area and it would be interesting for myself but almost certainly subpar for purpose. Am I just describing Wayfire? Without commenting on tech differences (I'm loving my mixed dpi wayland setup..), the social/community impact of X11 allowing UI/UX people to have their projects separate to the display server seems to have been significant.
- slondr 5y ago
  > Is there appetite in the Linux desktop dev community for a grab-and-go toolkit-agnostic Wayland display server that allowed DEs to plug in their own independent WM, decorations, animations, shell? Well, yes. It's called X11.
- boudin 5y ago
  There is intersting things going on to provide that. Wlroots landed wlr_scene api to make it much easier to create a compositor on top of wlroots. There is also riverwm which is quite interesting, built as a tiling wm but delegating wm management to an app, so allowing to create any quite of window management on it.

What's LXQt's Wayland story?

abrowne 5y ago

I'd guess Kwin.

yissp 5y ago
Is Kwin usable without plasmashell / the rest of KDE? I always thought they were pretty tightly integrated. I feel we're currently missing a minimalist stacking Wayland compositor in the vein of something like openbox.
- approxim8ion 5y ago
  KWin is indeed usable without the rest of KDE. It can be used as the window manager for XFCE or MATE, for example. Also, I'm not very educated in this matter, but isn't wlroots a fairly good Wayland compositor? Considering sway is built on it and supports both tiling and stacking, I think that might be worth a look.
  - pantalaimon 5y ago
    > It can be used as the window manager for XFCE or MATE, for example. But that's on X11 then, right?
    - approxim8ion 5y ago
      Yes, although KWin now supports Wayland quite a bit. There's an explanation here: https://community.kde.org/KWin/Wayland#Why_Plasma_needs_Wayland.3F https://community.kde.org/KWin/Wayland#Why_Plasma_needs_Wayl...
  - yissp 5y ago
    As I understand it, wlroots is more of a library that you can build a Wayland compositor on top of (sway being one example). It's not a compositor in and of itself. It still might be a good choice for LXQt if they do plan on supporting Wayland, though.
    - abrowne 5y ago
      One wlroots possibility would be Wayfire https://wayfire.org/ https://wayfire.org/
- ognarb 5y ago
  It's usable and some people in the automobile industry are interested in using it in an embedded context.

saxonww 5y ago

https://github.com/lxqt/lxqt/issues/10 https://github.com/lxqt/lxqt/issues/10

piaste 5y ago

Some sort of bring-your-own-compositor adventure at the moment, if I'm reading this issue correctly [0]. The thread did mention PaperDE [1] however , which you might want to look at if you're interested in a lightweight Wayland + QT environment. [0] https://github.com/lxqt/lxqt/issues/10 https://github.com/lxqt/lxqt/issues/10 [1] https://gitlab.com/cubocore/paper/paperde https://gitlab.com/cubocore/paper/paperde

akdor1154 5y ago

Tangent... There seem to be a fair few smaller (in community) DE projects (LXQt, XFCE, Cinnamon, Budgie, more I don't immediately recall) who are keen for Wayland support in principal but don't want to be landed with writing/maintaining their own display server. I know there are libs like wlroots, libweston, mir, but in practice it still seems to be too much to bite off to write a display server with one of these. Is there appetite in the Linux desktop dev community for a grab-and-go toolkit-agnostic Wayland display server that allowed DEs to plug in their own independent WM, decorations, animations, shell? In theory shell is doable already by xdg-shell, but splitting WM and decorations out would be a new approach for Wayland. Is this technically feasible? I have the urge to start writing one myself but I'm not experienced in this area and it would be interesting for myself but almost certainly subpar for purpose. Am I just describing Wayfire? Without commenting on tech differences (I'm loving my mixed dpi wayland setup..), the social/community impact of X11 allowing UI/UX people to have their projects separate to the display server seems to have been significant.

slondr 5y ago
> Is there appetite in the Linux desktop dev community for a grab-and-go toolkit-agnostic Wayland display server that allowed DEs to plug in their own independent WM, decorations, animations, shell? Well, yes. It's called X11.
boudin 5y ago
There is intersting things going on to provide that. Wlroots landed wlr_scene api to make it much easier to create a compositor on top of wlroots. There is also riverwm which is quite interesting, built as a tiling wm but delegating wm management to an app, so allowing to create any quite of window management on it.