| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T11536 KDeclarative breakup plan | ||
| Open | None | T13941 QML Bindings | ||
| Open | None | T11632 Move KCoreAddons QML bindings to KCoreAddons |
As a note, I think we don't want to "move" the wrappers exactly, but instead make use of Q_GADGET on the format and user classes.
Sounds good. I certainly would prefer if KCoreAddons would keep depending only on QtCore.
Yes, whatever glue code we can rid of by adapting the C++ API directly is even better.
Regarding dependencies, I understood that we'd make the QML dependencies optional everywhere, but have the bindings in the modules they provide API for nevertheless (to avoid having to depend on everything due to the binding module pulling in everything).
I certainly would prefer if KCoreAddons would keep depending only on QtCore.
I'm afraid, right now, I would still need some sort of QQmlEngine::registerType to make them usable.
That might change in Qt6, it might be something to push for.