[Kde-pim] Baloo Status

[Daniel Vrátil]

On Monday 20 of January 2014 17:16:06 Vishesh Handa wrote:
> Hey guys
> 
> We just have 5 weeks till the feature freeze, and we still have a lot of
> work to be done to remove Nepomuk completely. Plus we could use a lot of
> testing.

Hi,

> Most of the tasks seem to have fallen to Dan, and maybe we should help him
> out if we want this to happen in time for 4.13.

...and I'm kinda behind the schedule, because I had little time over Christmas 
and now exams to work on it. Next week is my last exam (hopefully), then I 
should be able to start working on it again. Any help is welcomed :-)

> Here is what needs to be done -
> 
> 1. Server side searching - Dan is working on this. I'm not sure what all
> needs to be done. Dan can fill us in :)

Server-side search is implemented on Akonadi server, the Akonadi::SearchJob is 
ready too (I extended the SEARCH command a bit). I have an experimental port 
of the IMAP resource to support server-side search which works, but the query 
is still hardcoded ATM in the resource, because of the reason below:

I'd like to use the Baloo's JSON query language as a "standard" for all 
queries, because we can easily send the same query to Baloo and Akonadi. Each 
resource that would want to support server-side search would just need to 
convert the JSON query into it's native query language. 

I don't know whether Baloo depends on kdepimlibs, but it would be nice if we 
could have a query serializer/parser class available in kdepimlibs, which 
could be use by resources, Akonadi::SearchJob and Baloo. Worst case scenario: 
we just copy the class from Baloo to kdepimlibs.


What is not yet done is persistent search (virtual collections). I'm still not 
sure how (and whether) to handle automatic search results updates.

> 2. Server Side tagging - Dan did a proof of concept implementation at the
> pim sprint, but it still needs a lot of work. Again, Dan can fill us in and
> we can start helping him.

On Akonadi-server side, this is pretty much copy-paste of flags implementation. 
It would be great if someone could help me by writing client-side code for it: 
Tag{Fetch,Create,Modify,Delete}Job, a TagModel (== ETM for tags only) and Tags 
notifications support in Akonadi::Monitor. This can be done without any 
knowledge of the server-side implementation, we just need to agree on new 
protocol commands and DBus API for notifications.

Cheers,
Dan

> 3. Email Notes - Currently email notes are stored in Nepomuk. We should
> probably store this as an attribute in Akonadi. Any volunteers?
> 
> 4. Porting MailCommon Search to Baloo - I've done most of this but it has
> not been tested at all. I thought I'd wait for (1), but I should start
> testing it.
> 
> 5. Porting the ContactSearchJob - Baloo uses a JSON based language. The
> ContactSearchJob has a lot of SPARQL queries. These should be replaced with
> json which Baloo understands. It's a simple task, but it needs to be done.
> Any takers?
> 
> --
> Vishesh Handa
> _______________________________________________
> KDE PIM mailing list kde-pim at kde.org
> https://mail.kde.org/mailman/listinfo/kde-pim
> KDE PIM home page at http://pim.kde.org/

-- 
Daniel Vrátil
KDE Desktop Team
Associate Software Engineer, Red Hat, Inc.

GPG Key: 0xC59D614F6F4AE348
Fingerprint: 4EC1 86E3 C54E 0B39 5FDD B5FB C59D 614F 6F4A E348
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20140120/661542d1/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/