The code is already in Baloo, under the namespace org.kde.baloo.experimental. It is being used only by KInfoCenter right now. The idea is that it'll not be used in anything critical until the API is stabilized. I don't see the need for API changes in the foreseeable future.
So maybe we can move it under the main namespace in some time and after that start using it in stuff like applets, KRunner etc? -- Thanks Pinak Ahuja On 8 November 2015 at 16:20, David Faure <fa...@kde.org> wrote: > On Wednesday 19 August 2015 16:03:34 Pinak Ahuja wrote: > > I am planning to add a baloo-monitor model to baloo's Qml plugin. The > > problem is that we cannot guarantee API stability right now. Is > exporting a > > new plugin under the namespace org.kde.baloo.experimental acceptable or > is > > there some other way to go about it? > > Seems nobody replied to this. > > This kind of thing won't annoy packagers (because it's all interpreted > stuff), > but still, it will annoy users. Do you really want users to get a broken > plasma > applet (I assume this is where the QML plugin is going to be used?) after > upgrading KF5 because you would then have changed the API, and they > don't have a newer release of whatever-uses-that-API ? > > -- > David Faure, fa...@kde.org, http://www.davidfaure.fr > Working on KDE Frameworks 5 > >
_______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
