add kcm support for lxqt-confg

[antis81]

Our issues with lxqt-config vs KDE systemsettings is that those are concurring concepts:

• LXQt -> *.desktop files (docs??)
• KDE -> kcm binary plugins (https://techbase.kde.org/Development/Tutorials/KCM_HowTo)

This leads to a lot of redundancy and responsibility conflicts. For example take the "appearance" tool:

Sorry for it being in German (note to self: prepare a VM with English setup).

Adding kcm support to lxqt-config makes it both - light on resources and fully functional. This would:

a) introduce a standard (yeah, right!)
b) make life easier for packagers (kcm's in LXQt and KDE)
-> create a lxqt-systemsettings
c) reduce need of writing new config tools over and over

And the best part:
Since we are using similar licensing models we can actually reuse existing code! The integration should be relatively simple and result in having the "best of both worlds". The relevant parts are in kcmutils.

(Gnome is a different game though. I don't have experience with that. Anyone?)

[tsujan]

There may be a big misunderstanding here. systemsettings has no relation to LXQt. It's a QML monstrosity KDE devs have made for KDE. We never use kcm.

[stefonarch]

I like it too, but on the other side some users argue that it never feels like one piece, like an assembling.
I think our goal should be satisfying both needs as far as possible.

[antis81]

As @tsujan mentioned it:
I use KWinFT - like butter! (Attention: Manjaro is not Debian! 😄)

FYI:
Only adjustment that I had to make manually was the KDE task switcher (the Breeze/-dark/-dusk ones don't work!)
I use MediumDefault (works only with KWinFT!).
Since MediumDefault has a similar look to good old openbox task switcher, it doesn't "feel" too much different!

[tsujan]

I use KWinFT - like butter!

I'll try it again if I find some time. The last time I tried it, it had shaky animations; otherwise, it inherited all properties and settings of KWin.

[tsujan]

some users argue that it never feels like one piece, like an assembling.

Sadly, it may be seen so, only because of WM.

For obvious reasons, well-known DEs like XFCE and Cinnamon don't ruin what they've achieved by taking Wayland too seriously. Perhaps, we need a similar approach in the case of WM.

[tsujan]

I had a little time to try KWinFT again. After all, its installation is very easy and nothing needs to be changed after it.

I mostly use translucent windows with blurring. KWinFT's animations became choppy when more than 2 windows were shown, while KWin's are always smooth.

Window shading didn't work with KWinFT.

[antis81]

I mostly use translucent windows with blurring. KWinFT's animations became choppy when more than 2 windows were shown, while KWin's are always smooth.

Didn't test blurring with KWinFT (I don't need/want it anyway). I run 2 hardware setups:

1. "refurbished" (and now pretty cool 😎) 15+ year old MSI with 3.5GHz dual-core CPU, 4GB RAM and nvidia 8500GT graphics
   • dual-monitor setup (1080p DVI and 1600x900(?) VGA)
   • (note: openbox worked fine with this setup and only minor issues ("wrong" selection order turned DVI screen "black"). With kwin(ft) I didn't try -> likely the same using lxqt-config-monitor tool!
2. Laptop 4GHz quad-core; 16 GiB RAM + intel SoC graphics

Both setups don't show performance issues (window shadows are 🆗) and show similar footprint ~400-500MB. This also depends on Manjaro services -> e.g. disabling "check for updates" in pamac seems to save ~100MB).

Both KWin & KWinFT have issues with window resizing:
When a window "sticks" to one screen side, I cannot "widen" it via mouse drag gesture. Can be annoying at times (workaround is possible by moving the window and drag on oposite edge).

[tsujan]

For me, KWin and KwinFT's memory usages are the same: between 35 and 50 MiB. I don't use Manjaro's automation (didn't like pamac and uninstalled it; only use pacman in terminal).

[antis81]

Talking about complete LXQt + kwin(ft) RAM usage btw. (not much different to openbox).

[tsujan]

Talking about complete LXQt + kwin(ft) RAM usage

Yes, I know. KWin's resource usage is optimized and KWinFT inherits it.