< Baloo Revision as of 17:54, 13 February 2014 (view source)Vhanda (talk | contribs) (→KDEPIM)← Older edit Revision as of 13:21, 7 March 2014 (view source) Andrea (talk | contribs) Newer edit → Line 64: Line 64: Use Nepomuk1 and is optional. It just seems to use it as an importer for listing the indexed properties. 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. Revision as of 13:21, 7 March 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. Contents 1 Dolphin 2 KDEPIM 3 Amarok 4 Digikam 5 GwenView 6 Conquiere 7 Kamoso 8 Kdenlive 9 Nepomuk-WebMiner 10 Bangarang 11 Plasma Mobile 12 KTp 13 Tellico 14 KGet 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 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 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. When the Baloo APIs are finalized this cane 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. Retrieved from "https://community.kde.org/index.php?title=Baloo/NepomukPort&oldid=36779" Content is available under Creative Commons License SA 4.0 unless otherwise noted.