This was fixed a while ago.

Done in https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/595.

https://invent.kde.org/plasma/kwin/-/merge_requests/2925 removes the last use

https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1123

I now need to take care of the migration code and remove the code from Kate

The MR landed and all providers inside of Plasma have been ported.

https://invent.kde.org/frameworks/kcmutils/-/merge_requests/84 landed and is used n two Plasma KCMS, the next step is de-duplicating the about plugin stuff

In T13467#254255, @ngraham wrote:

Another option that we've been discussing recently:

1. We make a universal theme of some sort (using CSS, QML, or something else; exact format TBD)
2. We make a QStyle that is essentially a Kvantum-style theming engine that consumes the universal theme and applies it to Widgets-based apps
3. We make a QQC2 style that consumes the universal theme and applies it to QtQuick software, including (optionally) Plasma, without going through QPainter or the QStyle at all
4. We keep the existing Plasma QQC2 style that knows how to consume existing SVG-based Plasma themes, for compatibility's sake
5. We add a user-facing setting for apps to allow people to choose whether to have:
   • Their apps use the universal theme
   • Their apps use a different QStyle, such as Lightly or Kvantum
6. We add a user-facing setting for Plasma to allow people to choose whether to have:
   • Plasma use the same universal style as their apps
   • Plasma use a different universal style from the one being used for their apps
   • Plasma use an SVG-based Plasma 5 theme, which we deprecate in Plasma 6 but continue to support
7. In Plasma 7, we sunset support for SVG-based Plasma themes as well as generic QStyles (including Kvantum!) and only support the new universal theme--whatever it is we come up with

https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1770 addressed the remaining uses.

https://invent.kde.org/plasma/powerdevil/-/merge_requests/92

I realized that the logic @iasensio referred to was completely broken in it's current form in KRunner. https://invent.kde.org/frameworks/krunner/-/merge_requests/102/ addresses this.

As discussed in the weekly, this should be done now, because the QML port is unlikely to make it in time for Plasma6.

plasma-sdk: two issues remaining (use of Theme::pluginInfo and Applet::loadPlasmoid)

Used for folder preview plugins

systemsettings: only KServiceTypeTrader remaining

It nevertheless is a 6 blocker though, no?

ksysguard: obsolete?

breeze-gtk is mostly a bunch of CSS, no Qt involved, so not relevant here

Ah, not in the 6 group, therefore I missed it. So the conclusion there is to drop the plugin stuff entirely? That would solve the problem as well of course. It nevertheless is a 6 blocker though, no?

See T12248

https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1671 removes the last use

https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1667 takes care of the task manager part of this.

Second part: https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/904

Solved by https://invent.kde.org/plasma/kscreenlocker/-/merge_requests/64

First part: https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/896

The usage in the kded KCM is just compatibility for old-style kded plugins, that can be dropped once we are ready to break things

I will try to create a model for the query logic, this can then be used from QML & the KRunner plugin. Ideally the model can be reused for the kate profiles.

Personally, I would prefer a window. Another argument for this is that for the config we need a window anyways. Meaning it would be consistent.