Sparky 3.6 dev2 LXQt + KWin

[pavroo]

I've been playing with LXQt desktop (again).
This time, as one of our G+ community member suggested, I have rebuilt the system.
I added KWin as a default window manager and removed Openbox.
It's just a test, nothing else yet, but I am gonna build a new, testing iso image opposite to the dev1 version with Openbox.

The system with KWin needs a little more RAM than with Openbox and uses:
32 bit: 160 MB
64 bit: 250 MB
Both of them run with some basic visual effects enabled as default.

There are a few shots I made today.
Cube:

Full screen: http://sparkylinux.org/images/sparky36-lxqt-cube.png
Cylinder:

Full screen: http://sparkylinux.org/images/sparky36-lxqt-cylinder.png
Sphere:

Full screen: http://sparkylinux.org/images/sparky36-lxqt-sphere.png

[drew]

Nice  :D I can confirm Kwin works very well with Sparky lxqt, the only thing is like you said it requires a bit more resources, which is obviously a consideration given this is a lightweight DE meant for resource constrained machines. I have both Openbox and Kwin installed so I can switch between the two---a choice between eye candy or maximium speed. Here's another screenshot. The desktop has locked up on me twice, but I've been using it everyday for a month. It seems almost ready for a stable 1.0 release.

[MoroS]

I added KWin as a default window manager and removed Openbox.

Oh, you're gonna make the older hardware suffer a lot. ;) Kwin (just like compiz and deriatives) is a heavily composited window manager and as such it's recommended to run it on something that has a good OpenGL support (basically nVidia, AMD or newer Intel cards). It's basically anything but light. I don't think that older Intel chips (like 945, I have one, so I'll test it) will have the power to provide a seamless and efficient experience, so I would suggest against making it official (and it would also go against Sparky's policy on older hardware). And dropping the compositing from it (if still possible, haven't used it in a while) will reduce it to what OpenBox offers, so I would stick with OpenBox for lower RAM usage.

[pavroo]

would also go against Sparky's policy on older hardware

No, it will not be, it's just my private "experiment'.
Openbox is and will be the primary window manager for the spin.

[drew]

Interestingly Mint 17.1 has two window managers installed by default---Marco (lightweight) and Compiz (eye candy), so it might be possible to work something like that out. I would tend to agree with Moro that Openbox is probably the better default option, Kwin takes all of five clicks to install from the debian repos, so if people want that it's very easy to get  8).

[pavroo]

Code Select Expand

so if people want that it's very easy to get
That's true, but you have to be aware that there are a lot of Linux beginners in the world.
I've seen many times situations when some people can't find for example Firefox or Google-Chrome. This makes them angry or disappointed and they just put an iso to a bin.

That's why I'm gonna build the second dev2 image with KWin working out of the box to let some guys test it without technical/linux/etc knowledge.
Anyway If you still would like to test LXQt spin on an older machine use dev1 iso with Openbox as default window manager.

[J.Jay]

Hello

currently use the Xfce64 spin
was going to experiment with the Lxde64 (main version?) with a xfce-panel and maybe some other xfce modules
WONDERING
1. how the lxqt spin (dev) runs GTK stuff.   Exspecially the xfce-panel and plugins, 'gnome-gmail' and gooboox (wife loves the simplicity playing CDs and burning to mp3s)?

2. whats the resource usage compare LXDE vz LXQT vz Xfce?

[pavroo]

I use many gtk+ apps on lxqt (and razor-qt before) - works fine, but never tried to run xfce-panel on it.

The usage of lxde and xfce I posted here:
http://sparkylinux.org/sparky-3-4-3-4-1-tests/
LXQt should be placed in the middle of them.

[J.Jay]

Thank you for reply :)

going to try LXQT (I know dev version only)! ::)  On the live seems to take alot of RAM compared to the LXDE and the XFCE (in live mode)
wasn't sure about GTK apps running in

J.Jay
P.S. I'm going to experiment till 'breaks' anyways ;D