On Tue, Dec 1, 2015 at 4:24 PM, Kai Uwe Broulik <k...@privat.broulik.de> wrote: >> you can build any view you want on top of it and the API is > public and (should be) stable. > > Yes but some services require additional information and provide a QML UI for > that. And that one will look out of place if using Plasma Components and > used in a widget environment, or limited to basic styling when using QQC. > Making some constraints on how they're supposed to be presented could help, > which is where the system-wide Plasma UI it would invoke comes to mind. Not > sure how feasible that it, though. Just food for thought.
Ah, true. For the UI the plugins can provide, the plan is they should provide QQC-based code (or bare QtQuick for that matter), but we can hardly limit what the plugin uses. Aleix _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
