So I think there is some agreement that where we have a relevant 1-1 match we put it with the framework. i.e KIO. knotifications(?), kunitconversion, kconfig, kbookmarks, solid...
That still leaves a few items where we need imports which don't have a match: - Helper actions for QML - like qtextracomponents/clipboard, qtextracomponents/mouseeventlistener, qtextracomponents/columnproxymodel I think this might be worth making a tier1 module. If there are enough items to warrant it and if there's going to be enough outside interest. Also we should try to upstream these; Digia are currently remaking something like mouseeventlistener; which is just a waste of effort. - Custom QtQuickControl styled widgets that aren't upstream. I don't generally think it makes sense to merge these with the widgets. If you want to build the widgets you wouldn't want the QML imports, if you want the QML imports you don't want to build the widgets. David _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
