Difference between revisions of "Baloo/NepomukPort"

Jump to: navigation, search
 
(14 intermediate revisions by 8 users not shown)
Line 1: Line 1:
This page catalogs all the applications that are currently using Nepomuk, and will need to be ported to Nepomuk
+
This page catalogs all the applications that are currently using Nepomuk, and will need to be ported to Baloo.
  
Please note that Baloo is not a drop in replacement for Nepomuk. Since Nepomuk relied on RDF, they way applications used it was very different than how applications will use Baloo. Nepomuk was often the central storage medium in KDE. Baloo does not have one central database.
+
Please note that Baloo is not a drop in replacement for Nepomuk. Since Nepomuk relied on RDF, the way applications used it was very different than how applications will use Baloo. Nepomuk was often the central storage medium in KDE. Baloo does not have one central database.
  
 
= Dolphin =
 
= 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.
+
Dolphin has been completely ported to Baloo.
  
 
= KDEPIM =
 
= 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.
+
KDEPIM was a heavy user of Nepomuk.  
 +
 
 +
- Indexing - Ported <br/>
 +
- Searching - Ported <br/>
 +
- Tags - In Progress <br/>
  
 
= Amarok =
 
= Amarok =
Line 17: Line 21:
 
Making Amarok share their index with Baloo is not being considered at this time. It could be done in the future as a separate project.
 
Making Amarok share their index with Baloo is not being considered at this time. It could be done in the future as a separate project.
  
= Digikam =
+
= digiKam =
 +
digiKam was succesfully ported to Baloo. Old implementation was completely dropped, in favor of a small extension of metadata read/write functionality. When image metadata is read or written, it is also updated with Baloo.
 +
For better integration with digiKam, a more flexible File Monitor from Baloo is desired.
  
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.
+
[https://bugs.kde.org/show_bug.cgi?id=332665 See this entry from bugzilla about this topic]
  
 
= GwenView =
 
= GwenView =
  
Requires porting
+
Ported
  
 
= Conquiere =
 
= Conquiere =
  
 
Conquiere heavily depended on Nepomuk as its primary storage mechanism. It will need to be reworked to have a new storage medium.
 
Conquiere heavily depended on Nepomuk as its primary storage mechanism. It will need to be reworked to have a new storage medium.
 +
 +
Might get canceled. Conquirere without Nepomuk (and SQL for example) is basically just [http://quickgit.kde.org/?p=kbibtex.git KBibTeX]. Adding more features to KBibTeX is thus a way better solution here.
  
 
= Kamoso =  
 
= Kamoso =  
Line 36: Line 44:
  
 
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.
 
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.
 +
 +
The Nepomuk code was meanwhile removed and the last [http://commits.kde.org/kdenlive/4d7a61020fc20990c68bbd556a4782b5632b63e8 traces in CMakeLists file] as well.
 +
 +
When the Baloo APIs are finalized this can be ported to store the data in the extended attributes of the file.
  
 
= Nepomuk-WebMiner =
 
= Nepomuk-WebMiner =
  
 
Will need to be reworked.
 
Will need to be reworked.
 +
 +
= Bangarang =
 +
 +
Bangarang has not seen any real development in almost 1.5 years. If it needs to be ported it will need to be heavily reworked. It would be nice if someone created a multi-media library on top of Baloo which all multi-media related applications could use - Plasma Media Center, Amarok and Bangarang.
 +
 +
= Plasma Mobile =
 +
 +
We've spoken with one of the main developers, Marco Martin, and Baloo meets all the required needs. The porting is not trivial, but it's not complex. It just needs to be done.
 +
 +
= KTp =
 +
 +
Kpeople has been ported away from Nepomuk.
 +
 +
= Tellico =
 +
 +
Use Nepomuk1 and is optional. It just seems to use it as an importer for listing the indexed properties.
 +
 +
= KGet =
 +
 +
Use Nepomuk1 and is optional.
 +
 +
= Plasma Media Center =
 +
 +
Plasma Media Center 1.3 (to be released in June 2014) supports both Baloo and Nepomuk.

Latest revision as of 19:41, 19 August 2014

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

Please note that Baloo is not a drop in replacement for Nepomuk. Since Nepomuk relied on RDF, the way applications used it was very different than how applications will use Baloo. Nepomuk was often the central storage medium in KDE. Baloo does not have one central database.

Dolphin

Dolphin has been completely ported to Baloo.

KDEPIM

KDEPIM was a heavy user of Nepomuk.

- Indexing - Ported
- Searching - Ported
- Tags - In Progress

Amarok

The Amarok project provided an additional Nepomuk collection which could be used if the user did not want Amarok to index all their music files. Removing this Nepomuk collection does NOT remove any functionality from Amarok.

Making Amarok share their index with Baloo is not being considered at this time. It could be done in the future as a separate project.

digiKam

digiKam was succesfully ported to Baloo. Old implementation was completely dropped, in favor of a small extension of metadata read/write functionality. When image metadata is read or written, it is also updated with Baloo. For better integration with digiKam, a more flexible File Monitor from Baloo is desired.

See this entry from bugzilla about this topic

GwenView

Ported

Conquiere

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

Might get canceled. Conquirere without Nepomuk (and SQL for example) is basically just KBibTeX. Adding more features to KBibTeX is thus a way better solution here.

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.

The Nepomuk code was meanwhile removed and the last traces in CMakeLists file as well.

When the Baloo APIs are finalized this can be ported to store the data in the extended attributes of the file.

Nepomuk-WebMiner

Will need to be reworked.

Bangarang

Bangarang has not seen any real development in almost 1.5 years. If it needs to be ported it will need to be heavily reworked. It would be nice if someone created a multi-media library on top of Baloo which all multi-media related applications could use - Plasma Media Center, Amarok and Bangarang.

Plasma Mobile

We've spoken with one of the main developers, Marco Martin, and Baloo meets all the required needs. The porting is not trivial, but it's not complex. It just needs to be done.

KTp

Kpeople has been ported away from Nepomuk.

Tellico

Use Nepomuk1 and is optional. It just seems to use it as an importer for listing the indexed properties.

KGet

Use Nepomuk1 and is optional.

Plasma Media Center

Plasma Media Center 1.3 (to be released in June 2014) supports both Baloo and Nepomuk.


This page was last edited on 19 August 2014, at 19:41. Content is available under Creative Commons License SA 4.0 unless otherwise noted.