KConfigWidgets:
- KStandardActions T12148:
- Move somewhere else outside KConfigWidgets
- KRecentFilesAction requires config
- KRecentFilesAction uses KSelectAction but incorrectly?
- Move somewhere else outside KConfigWidgets
- KCModule T12150:
- It's a QWidget, there's also KCModuleQml, do some inheritance or composition thing
- or move every KCM stuff into KCMUtils?
- It's a QWidget, there's also KCModuleQml, do some inheritance or composition thing
- KCodecAction:
- Kate has its own, merge?
- KColorScheme T11587:
- Why in kconfigwidgets? Needed all over the place
- Add some features to QPalette (like positive, negative, neutral colors)?
- Check if Windows, macos, Android, etc have semantic colors
- Does it need KConfig? https://phabricator.kde.org/T11587
- KColorSchemeManager:
- a widget with a model of colors and something to set custom color scheme
- Split model and setting logic somewhere else?
- Make it a standard action for them menu?
Needs "system color" option to reset custom colorD25877
KRecentFilesAction T12246:
- Get rid of KConfig, store INI in some state home dir instead
KConfigDialogManager
- Remove redundant KConfigDialogManager::KConfigDialogManager(QWidget *parent, KConfigSkeleton *conf) and KConfigDialogManager(QWidget *parent, KConfigSkeleton *conf) See(D26361 T12480)
Move everything related to showing and providing config to KCMUtils.
Make KConfigWidgets be widgets using KConfig (ktipdialog, KRecentFilesAction)
Once all executed there's not much left. Kill it?