[Kde-imaging] [Bug 195106] Kipi should be able to lock photos in host application

Gilles Caulier caulier.gilles at gmail.com
Thu Jun 4 08:07:29 CEST 2009


https://bugs.kde.org/show_bug.cgi?id=195106





--- Comment #3 from Gilles Caulier <caulier gilles gmail com>  2009-06-04 08:06:29 ---
>How do the affected KIPI plugins store their lists? As KUrls?
>As KipiImageInfo?

This depend. For multithreaded tool, KUrl is used, for others KipiImageInfo. At
least Kurl list is always generated from KipiImageInfo is main thread.

In fact, i think lock item feature is very important in digiKam, outside
kipi-plugins/libkipi because of new BatchQueueManager. Lock items must be done
internally in digiKam following BQM activity and after extended to
kipi-interface.

I think libkipi no need to be changed a lots here. The main implementation
staying in kipi host core + kipi host interface.

To resume :

1/ a plugin ask to host to play with items. 
2/ host lock items because there are processed by an external tool.
3/ in gui, a mark must be visible over icon to bring user about lock state.
4/ when plugin is done, kipi host unlock items.

I think 1/ and 4/ need small change in libkipi to request lock/unlock in kipi
host from plugin.

Gilles

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the Kde-imaging mailing list