@CvWild Glad you agree. I mean customize your desktop as you like with custom applets. That is what Plasma is excellent for. I just don’t want the desktop getting messed up with poor design choices like with what’s going on with modern Windows today (AKA Winsuck 11 presently). lol
The main differences are:
- Built-in applets are guaranteed to work in future Plasma versions.
- Built-in applets can contain native C++ code.
1 Like
Built-in applets certainly aren’t immune to breakage 
But yes, benefit of C++ over QML makes perfect sense (performance, linkage, etc).
Just a few more thoughts here:
As a blind test, I tried the two external applets linked in this thread and I’m sorry to say they are indeed lacking.
Control Centre 6 was unable to init on my system due to what i’m guessing are recent QT changes in 6.2 (case in point 
).
KDE Control Station loads and renders fine at first glance, but it is misreporting my laptop battery (likely due to thinkpad, almost worth a report to the dev).
I read further up from @WildeGreen:
The Plasma Mobile Quick Settings are gorgeous, port those to desktop and call it a day.
This sounds like the best solution bar none. No need to reinvent the wheel if the controls and Breeze styling are already all there. I’m sure it’s much more complicated than it seems, but if someone was motivated enough i’m sure it could be done.
1 Like
Yes, the Plasma Mobile Quick Settings should be ported to desktop just like Apple dit it.
Conceptually, I agree, strongly. However:
I think the difficulty is that Plasma Mobile’s shell isn’t designed to be as modular as the desktop shell. Therefore, things like its control centre are more monolithically integrated. It’d need be rearchitected to be packagable into a plasmoid with the same codebase.