[Digikam-devel] Digikam and Nepomuk

[Veaceslav Munteanu]

I predicted that something was going to change... but I didn't expect
to be that much. :))

So nepomukwrap , nepomukquery and nepomukwatcher are only small files
that holds almost all api calls. Must be easy to port. Yet I didn't
foresee a full drop and main digikamNepomukService class that depends
on NepomukService.

Basically without Something as NepomukService in Baloo, this piece of
code is dead.



On Sat, Jan 18, 2014 at 1:06 PM, Gilles Caulier
<caulier.gilles at gmail.com> wrote:
> 2014/1/17 Vishesh Handa <me at vhanda.in>:
>> Hey guys
>>
>> As some of you might have heard. KDE is going to be dropping support for
>> Nepomuk with its 4.13 release.
>
> Seriously ???
>
> Veaceslav Munteanu has shared a lots of time this summer to fix
> Nepomuk support. KDE something has sad API support in time...
>
> What's we can do to port Nepomuk to this future "Baloo" framework ?
>
> Gilles Caulier
>
>>
>> Nepomuk has had a nice rice, but it has various fundamental problems which
>> cannot be fixed. In its place a new project has been started called Baloo
>> which does not rely on RDF and has very specific goals.
>>
>> From what I understand, Digikam has recently re-enabled support for
>> synchornizing Nepomuk tags/ratings and comments via a dedicated service which
>> does this two way synchronization.
>>
>> Given that Nepomuk and Baloo do not share the same data, maybe shipping with
>> it might not be the best idea. What do you guys think?
>>
>> You can read more about Baloo over here [1]
>>
>> PS: Please keep me CCed.
>>
>> --
>> Vishesh Handa
>>
>> [1] http://community.kde.org/Baloo
>>
>> _______________________________________________
>> Digikam-devel mailing list
>> Digikam-devel at kde.org
>> https://mail.kde.org/mailman/listinfo/digikam-devel