<br><br><div class="gmail_quote">2008/11/29 Aurélien Gâteau <span dir="ltr"><<a href="mailto:aurelien.gateau@free.fr" target="_blank">aurelien.gateau@free.fr</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>> Aurélien,<br>
><br>
> As i said to coding sprint, I'm working to a new batch queue manager for<br>
> digiKam. A first preview is available on my flickr account :<br>
><br>
> <a href="http://www.flickr.com/photos/digikam/3065212027/sizes/o/" target="_blank">http://www.flickr.com/photos/digikam/3065212027/sizes/o/</a><br>
><br>
> Like you can see on the bottom of Queue manager window, i plan to plugin<br>
> all kipi batch tools here. For the moment, it's limited to use internal<br>
> tools from digiKam core.<br>
><br>
> This is want mean that later libkipi need to be patched in this way. But<br>
> it's not for the moment (:=)))<br>
<br>
</div>Oh, yes I remember now. Just to make sure we are talking about the same<br>
thing: The idea is to be able to write a new type of KIPI plugins,<br>
which would be able to work on image data and have the host app<br>
implement a batch manager which can call these plugins. Is that it?</blockquote><div><br>yes; but plugins structure is just adapted to export batch core component only to host.<br><br>Currently, my batch Queue manager use core libs from digiKam, where a lots of code can be used to play with image data (color corrections for ex.)<br>
<br>I have implemented a definition of Batch Tools like tis :<br><br>input image path <br>+ -> Batch Tool -> output image path<br>tools settings<br><br>The Batch tool component export settings in a class container + a widget where settings can be adjusted by user in Queue Manager.<br>
<br>My idea for the future, is to adjust batch tool plugins in this way: we export batch core implementation + settings widgets + settings data to use it somewhere in host application....<br><br>The advantage of Queue Manager is to be able to process more than one batch action at the same time. Batch tools can be serialized one by one.<br>
<br>Also, in the same time, we must preserve the current Batch tool plugin dialogs, in case of host cannot play with the new Batch Tool interface. Of course, in this case, plugins can only process one action by images.<br>
<br>My plan in first is to implement a version using digiKam core components, and hack,improve, and polish Batch Tools interface to proposal a new libkipi extension. This will be for later KDE 4.2, when kipi-plugins 0.2.0 and digiKam 0.10.0 final releases will be published.<br>
<br>best<br><br></div></div>Gilles <br>