[Digikam-devel] External tools

[Yuri Samoilenko]

Please correct me if i make a mistake.
BQM processing files as pipeline(one tool applied on result of another) but
on each file separately, not on whole image group.
The best sollution will be to implement group processing into BQM
engine(into batchTool) to allow tool operate on whole file group. And to
export KIPI export plugins as such batch tools. Right?


2013/10/26 Gilles Caulier <caulier.gilles at gmail.com>

>
> With kipi, we have this problem with all export tools which are a stand
> alone processing in a dedicated dialog.
>
> A solution can be to export kipi tool settings + core operations to kipi
> host application, but this need to change a lots libkipi API and patch
> whole plugins. Typically, a student have been planed to work a ths project
> with GSoC, but he have found a real job and project have been canceled. See
> details here :
>
>
> https://community.kde.org/GSoC/2013/Ideas#Project:_Integrate_KIPI_Export_Plugins_directly_in_the_GUI_of_KIPI_host_applications
>
> The KDE service way is too... limited and cannot be serialized in BQM.
>
> My proposal is more simplest : In BQM, patch Queue "Target" settings to
> include new options to perform "export features". This can include tarball
> processing, export to a remote computer, export to a web service, etc..
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-devel/attachments/20131026/7290a1d2/attachment.html>