Jump to content

Baloo/NepomukPort: Difference between revisions

From KDE Community Wiki
Vhanda (talk | contribs)
Vhanda (talk | contribs)
Line 7: Line 7:
= KDEPIM =
= KDEPIM =


* Simple Searching done
KDEPIM was a heavy user of Nepomuk. It gains the most by migrating to Nepomuk. The indexing infrastructure has already been ported to Baloo. The tagging and search backend still requires porting.
* Contact Completion done
* Email Search - Not done
* ContactSearchJob - Needs work


= Amarok =
= Amarok =

Revision as of 15:33, 17 January 2014

This page catalogs all the applications that are currently using Nepomuk, and will need to be ported to Nepomuk

Dolphin

Dolphin has been completely ported to Baloo. All traces of Nepomuk have been removed. There are some minor bugs which need to be addressed, but for the most part it is feature complete.

KDEPIM

KDEPIM was a heavy user of Nepomuk. It gains the most by migrating to Nepomuk. The indexing infrastructure has already been ported to Baloo. The tagging and search backend still requires porting.

Amarok

Amarok has a separate Nepomuk collection. Porting this is going to be next to impossible as it creates huge sparql queries.

Digikam

With the latest Digikam, it allows tags/rating to be synchronized with Digikam's database. This is done by running a process which continuously monitors the Digikam and Nepomuk database and performs 2 way synchronization. Considering that Baloo uses extended attributes to store tags, it might be easier to integrate this with Digikam.

GwenView

Requires porting

Conquiere

Conquiere heavily depended on Nepomuk as its primary storage mechanism. It will need to be reworked to have a new storage medium.

Kamoso

Needs porting. Just using tags, should be very simple.

Kdenlive

Uses Nepomuk to store the license information of a file. It's not integral to the application, and is just a nice addon. Considering that this requires Nepomuk to be running, it does not seem like a big loss.

Nepomuk-WebMiner

Will need to be reworked.