Hey Boudhayan,
It's nice that you are stepping up for maintaining baloo. I have no
objections to that and will try to help you out whenever needed :)
Cheers,
Pinak
--
Thanks
Pinak Ahuja
On 11 September 2016 at 19:40, Boudhayan Gupta wrote:
> Hi,
>
> On 11 September 2016 at 22
> On Feb. 25, 2016, 9:18 p.m., Pinak Ahuja wrote:
> > src/externalextractor.cpp, line 104
> > <https://git.reviewboard.kde.org/r/127179/diff/1/?file=445488#file445488line104>
> >
> > You should use the asynchronous api instead of blocking the event loo
tps://git.reviewboard.kde.org/r/127179/#comment63213>
You should use the asynchronous api instead of blocking the event loop by
calling waitForFinished()
Connect a slot to the QProcess::finished signal and let it handle the
output of the QProcess.
- Pinak Ahuja
On Feb. 25, 2016, 6:32 p.m.,
e 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 wrote:
> On Wednesday 19 August 2015 16:03:34 Pinak Ahuja wrote:
> > I am planning to add a baloo-monitor m
? I already
submitted https://git.reviewboard.kde.org/r/124962/ to fix the behaviour you
are mentioning.
- Pinak Ahuja
On Sept. 9, 2015, 1:58 p.m., Giuseppe Calà wrote:
>
> ---
> This is an automatically generated e-mail. To rep
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
