How long did you use KDE? Do you find LXQT lacking in any way?LXQT sounds like a good one to me.
I've switched from KDE to LXQT on all my machines recently.
How well is LXQt supported these days? When it first came out, I remember it not working too well.On desktop I prefer KDE, but I think LXQt would be a nice fit for pyra.
Well the main problem would be if the gpu drivers support wayland and we'd need a DE that supports it, which Gnome seems to do.With version 3.14, Gnome supports running the desktop using Wayland. The Gnome compositor can be run without using X, and will act as a Wayland system compositor. It is considered stable for production use, but there are still some features that are not yet supported (refer Gnome documentation). Under this desktop, applications using X will run using XWayland.
To start up a Gnome Wayland session, gdm login manager needs to be used, and the user must select the "Gnome on Wayland" session before logging in.
With any open source driver you can now start "Gnome on Wayland" from GDM as a special session.
Thanks for the correction!There were some issues using wayland, framebuffer access or somesuch. It will probably be an option at some point, but we can't really jump in with both feet at this time without knowing whether it will be up to the task when we need it to be. Let's get a working system using known components first and then see if we can make all the same stuff work on Wayland.
Side note: XWayland doesn't emulate X. It creates an X server and runs the application inside it. The window contents of that X server are rendered by wayland.
But it should also mean the graphical work the cpu is not doing is done by the gpu more efficiently, so gpu can have much lower clock while only displaying 2D stuff, and the CPU can be lower frequency/cores as well. won't that save in the power?TI is supporting Wayland with the current 3D drivers, but not X anymore, so that shouldn't be the issue.
However, wayland constantly uses the 3D driver, which means it's an additional power drain.
And yes, the current LXQT version runs very well. Haven't found anything I'm missing. But then again, I don't use Widgets, so if you use KDE because of widgets, you'll miss somdething.
Android phones get a decent battery life?Thanks for the correction!There were some issues using wayland, framebuffer access or somesuch. It will probably be an option at some point, but we can't really jump in with both feet at this time without knowing whether it will be up to the task when we need it to be. Let's get a working system using known components first and then see if we can make all the same stuff work on Wayland.
Side note: XWayland doesn't emulate X. It creates an X server and runs the application inside it. The window contents of that X server are rendered by wayland.
But it should also mean the graphical work the cpu is not doing is done by the gpu more efficiently, so gpu can have much lower clock while only displaying 2D stuff, and the CPU can be lower frequency/cores as well. won't that save in the power?TI is supporting Wayland with the current 3D drivers, but not X anymore, so that shouldn't be the issue.
However, wayland constantly uses the 3D driver, which means it's an additional power drain.
And yes, the current LXQT version runs very well. Haven't found anything I'm missing. But then again, I don't use Widgets, so if you use KDE because of widgets, you'll miss somdething.
I'm just thinking portable devices such as android phones and tablets are drawing in 3D surfaces the whole time and still get decent if not excellent battery life.
Tell that to the battery pack that I have to keep permanently attached to my phone.I'm just thinking portable devices such as android phones and tablets are drawing in 3D surfaces the whole time and still get decent if not excellent battery life.