It's odd that e.g. ConfigModule resides in the KDeclarative framework, shouldn't there be a framework that provides both the QML and the Widget based equivalent currently in KConfigWidgets?
Idea: Move KCModule from KConfigWidgets to kcmutils and also move ConfigModule there? or in another new framework altogether
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T11536 KDeclarative breakup plan | ||
| Open | alex | T12127 move ConfigModule next to KCModule widget counter part |
ConfigModule would be better somewhere else, ideally in the same repository than KCModule (since they solve the same problem, it's just Quick vs Widgets here). There are two ways forward depending on how KConfigWidgets can be realistically streamlined:
both KCModule and ConfigModule can be moved into the kconfig repository (under widgets and quick subfolders)
they can't move in kconfig, then we should both move them to KCMutils instead?
Moving this to done, because I have a draft MR for it https://invent.kde.org/frameworks/kcmutils/-/merge_requests/121