From kde-imaging Thu Feb 19 15:22:17 2009 From: =?ISO-8859-1?Q?Aur=E9lien_G=E2teau?= Date: Thu, 19 Feb 2009 15:22:17 +0000 To: kde-imaging Subject: Re: [Kde-imaging] (No more) batch plugins in kipi Message-Id: <499D7929.6020403 () free ! fr> X-MARC-Message: https://marc.info/?l=kde-imaging&m=123505696916557 Gilles Caulier wrote: > 2009/2/19 Aurélien Gâteau : >> Gilles Caulier wrote: >>> Batch Queue Manager is developed in digiKam core for multiple reason: >> [snip valid reasons] >> >> OK, I see your point. >> >>> I'm sure you can do something similar in Gwenview >>> >>> But for kipi, i have others plan : export widget + background process >>> code from all defined batch plugis to be able to use it in a dedicated >>> manager defined in the host and based on a extended api from libkipi. >>> Typicaly, i will use a part of implementation from current Batch Queue >>> Manager and put it to likipi. I will patch some plugins as >>> DngConverter to export settings widget and DNG converter core to be >>> able to use it in Batch Queue Manager as if it have been implemented >>> in digiKam core. >>> >>> Of course, stand alone version of current batch plugins will still >>> available, nothing change for Gwenview. >>> >>> For the moment Batch Queue Manager work, but not yet perfect. I will >>> not touch libkipi for the moment and i will wait to have a more stable >>> implementation. >> This sounds good. I think it would be a good idea if I port the batch >> plugin meanwhile: >> - It will provide users with a feature they miss until the new >> infrastructure is there. >> - It will be easier to refactor the code to integrate in the new >> infrastructure if it is already using KDE4. >> >> What do you think about this? > > Fine for me... OK, then I'll try to start working on it next week. Aurélien _______________________________________________ Kde-imaging mailing list Kde-imaging@kde.org https://mail.kde.org/mailman/listinfo/kde-imaging