It has been explaine, don't reply instead reread those messages. This is completely unacceptable behaviour. You're sabotaging your own cause.

We spoke in a previous task about this. You cannot just reopen the same ticket again and again.

If so, KDE should add a clear exception to the KDE Vision for benevolent Western

I will fix krfb, I know there are pending patches for yakuake to port to layer-shell which are ready to go when it can rely on Qt 6

Relevant commit: https://invent.kde.org/frameworks/kpackage/-/commit/cfb69e21fb0aad92f403487b4c8a75b2b0bc8041

Indeed

I tried porting Plasma and hit some major brick walls:

Key difference.

KWallet has a "folder" and "appID" "key"

In T11080#277256, @fusionfuture wrote:

+1 to revive this goal

Sandbox exploitation seems a reason to not have this available :/

Sounds more like users working round the limited API of kwins scripting. No need to use DBus there. If that's the only reason I'll export something more suited there. I need a Qml wrapper for Plasma6 anyway.

Where does this situation come up for clients to need to?

Sure. Help yourself.

Native resources used:

can we port to kirigami's class?

and do WidgetExplorer to the same

This is potentially duplicated with IconItem's fade.

Fades between two items without the brightness bug you get with changing opacity on two items.

This seems questionable now. Propose to drop.

Action plan:

• This gets turned into a dialog
• Default Applications gets a button to launch this (solving a plasma-settings problem)
• Default Applications might get a simple use surfacing common actions to set "preferred video player" etc., but leave advanced stuff to this dialog

There's a QtQuick port here: https://invent.kde.org/smitpatil/kwingamma

I think this ShaderEffect can be got rid of. We're using layer effects