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
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 oth
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?
--
Pinak Ahuja
__
