[Digikam-users] Digikam and the KDE
caulier.gilles at gmail.com
Sun Oct 9 18:00:39 BST 2011
A lots of people clam that digiKAm is too relevant of KDE and you want
to ncrease again the depency ?
We have worked hvery hard to make a database interface delegate to
image anagement. I won't to ask to others developers that we trash all
this work to replace it by Nepomuk stuff.
I don't have any idea about Nepomuk stability... I know the status of
digiKam DB interface, and it's not perfect.
Marcel as written an interface between digiKam DB and Nepomuk. It's
enough. If somebody want to improve it, why not, but we will never
replace digiKam DB by Nepomuk.
It's just my developper viewpoint of course...
2011/10/9 Anders Lund <anders at alweb.dk>:
> On Søndag den 9. oktober 2011, jdd wrote:
>> Le 09/10/2011 16:16, todd rme a écrit :
>> > whole point of both nepomuk and akonadi is "having a more stable,
>> > dedicated basis for storage".
>> if so, why is nepomuk labelled "search on the desktop"?
> Nepomuk deals with metadata + file indexing. All documents can be
> tagged/rated/commented, like we can do in digikam in fact, and metadata is
> indexed from - potentially - all file types with nepomuk, similar to what
> digikam does with images. Files containing text is also indexed for text
> The difference from digikam is that metadata known to nepomuk is available to
> any application interrested, through a standard interface, so that metadata
> produced by one application is available for others.
> With digikam, this means that if metadata is shared through nepomuk, they can
> be used for example in file manager or other image viewers etc. Right now, to
> send images pr email for example, you would select them in digikam and then
> use the built in send function. With nepomuk, you could go the other way round
> and search for images with a certain tag or other metadata from the attach
> file function of kmail. Etc etc ...
> Digikam-users mailing list
> Digikam-users at kde.org
More information about the Digikam-users