Status | Assigned | Task | ||
---|---|---|---|---|
Open | None | T12102 Meta-Task: Plasma Framework 6 | ||
Open | None | T12141 KActionCollection: do we need it really, in Plasma-Framework? |
Comment Actions
At quick glance most of it can probably be replaced with a Map<QString, QAction>.
Non-trivial parts are loading/saving shortcuts:
- https://invent.kde.org/frameworks/plasma-framework/-/blob/master/src/plasma/corona.cpp#L471
- https://invent.kde.org/frameworks/plasma-framework/-/blob/master/src/plasma/private/applet_p.cpp#L410
Perhaps we need a utility method to load/save a map of actions to KConfig
Comment Actions
Instead of exposing them as QMap I'd rather add a function that exposes the actions individually, like in https://invent.kde.org/frameworks/kio/-/merge_requests/997
It could be done based on string keys, but for known "standard" actions an enum would be nicer
Comment Actions
This could still be backed by a KActionCollection internally, but it would give us more flexibility in the long term by not exposing that in the API
Comment Actions
For systemtray's inner containment we'd also need a way to add actions, but that doesn't require exposing the full KActionCollection either