[Digikam-devel] Changes in libkipi

[Gilles Caulier]

2010/6/20 Marcel Wiesweg <marcel.wiesweg at gmx.de>:
>
>> Hello everyone!
>>
>> I've added a function in libkipi that returns the tagModel from digikam.
>> I've needed a new function instead of the existing selection widget because
>> selection widget had some extra options that are not needed in gpssync(like
>> the search tool or album selection tool).
>>
>> The code from libkipi is here [0] (interface.h, interface.cpp) and the
>> changes from digikam's kipiinterface are here [1] (kipiinterface.h,
>> kipiinterface.cpp).
>>
>> If you have any observation or suggestion about this, please tell me.
>
> - a model or a widget? Getting a widget (for digikam, a TagTreeView) will
> ensure consistent behavior with widgets in the application.

I'm agree with marcel, creating a template widget in libkipi to
display  a tagtreeview will be better.

The widget creation must be done in kipi host application. To delegate
this on digiKam, this will give an homogenous view of tree view, and
can be shared with another plugins as well.

Don't forget that plugins are shared with others hosts as gwenview or
kphotoalbum which have a different view for keywords management.

As, i have already said previously, this is already done like this for
collection selection widget used in HTMLExport or FlashExport for ex.
Code is there :

http://websvn.kde.org/*checkout*/trunk/KDE/kdegraphics/libs/libkipi/libkipi/uploadwidget.h?revision=911273

http://lxr.kde.org/source/extragear/graphics/kipi-plugins/flashexport/selectionpage.cpp#58

http://lxr.kde.org/source/extragear/graphics/digikam/utilities/kipiiface/kipiuploadwidget.h

Gilles

Gilles