digiKam 6.0.0 BQM and export to web services
Gilles Caulier
caulier.gilles at gmail.com
Sun Jan 21 14:24:46 GMT 2018
A first important stage to this task have be done with this commit :
https://commits.kde.org/digikam/061fafd3674d0a4b1cbf22fa63ea81df2ca87272
It's not yet completed. See my commit comments.
Gilles Caulier
2018-01-20 13:18 GMT+01:00 Gilles Caulier <caulier.gilles at gmail.com>:
> Hi all,
>
> For 6.0.0, i plan to changes several features in Batch Queue Manager about
> to export automatically a list of items from a list to a remote web service.
>
> Typically, you put the items to batch process in BQM, you set the remote
> web service to export the queue at end, you press run and you can take a
> coffee. Welcome to DK 2018 (:=)))...
>
> I collected a lots of entries in bugzilla about this topic :
>
> https://bugs.kde.org/show_bug.cgi?id=133137
>
> ==> resolved in BQM as well.
>
> https://bugs.kde.org/show_bug.cgi?id=194811
>
> ==> resolved in BQM as well, all is multithreaded.
>
> https://bugs.kde.org/show_bug.cgi?id=221704
>
> ==> resolved with BQM of course.
>
> https://bugs.kde.org/show_bug.cgi?id=235572
>
> ==> in BQM using ssh qt interface.
>
> https://bugs.kde.org/show_bug.cgi?id=262323
>
> => In BQM export tools will write post processed file in a temp album
> automatically.
>
> https://bugs.kde.org/show_bug.cgi?id=278343
>
> ==> Thanks to BQM to provide all editor tools in batch process (:=)))...
>
> https://bugs.kde.org/show_bug.cgi?id=287811
>
> ==> More and less done with OAuth2 for the logging. For the transfert,
> typically, all recent web service must use ssl based communication. Please
> confirm this point if you know the response...
>
> https://bugs.kde.org/show_bug.cgi?id=287813
>
> ==> Must be included in new BQM export settings.
>
> https://bugs.kde.org/show_bug.cgi?id=297290
>
> ==> BQM has already a tool dedicated for this task.
>
> https://bugs.kde.org/show_bug.cgi?id=298020
>
> ==> Done by OAuth2 automatically ??? We cannot use KF5Wallet here. It's
> KDE only solution, and i don't want to be more KDE dependent. The goal is
> to move DK to a pure Qt5 application in the future.
>
> https://bugs.kde.org/show_bug.cgi?id=309725
>
> ==> Flickr export tool has these kind of options. So it's specific to each
> web service and the relevant code must be included in export tool low level
> implementation.
>
> https://bugs.kde.org/show_bug.cgi?id=313816
>
> ==> In BQM already. this will factorize a lots of code in export tool
> (:=)))...
>
> https://bugs.kde.org/show_bug.cgi?id=317611
>
> ==> Automatically done by DMetadata from digiKam core.
>
> https://bugs.kde.org/show_bug.cgi?id=317688
>
> ==> BQM can rename files before to export (:=))))....
>
> https://bugs.kde.org/show_bug.cgi?id=346128
>
> ==> BQM can rotate files automatically before to export (:=))))....
>
> https://bugs.kde.org/show_bug.cgi?id=351366
>
> ==> Removing metadata from file remove tags already in BQM.
>
> There are more entries relevant of this project but there are more
> specifics and must be managed in a second stage.
>
> To resume my plan.
>
> - In BQM queue settings, add a new view to setup an export stage where
> user can choose a web service as flickr, imgur, dropbox, google, facebook,
> etc... This view must include the login info and the target dir in remote
> server to host items previously processed by the queue.
>
> - add new BQM low level tools to manage the export operation with the
> network. Each tool must include :
>
> * A stage to log on user in remote server.
> * A stage to list remote directory.
> * A stage to list features from remote web service.
> * A stage to send files to remote server.
> * A stage to log off user in remote server.
>
> - each new BQM export tools will include a customized settings widget to
> host web service properties.
>
> VoilĂ . All constructive comments are welcome.
>
> My best
>
> Gilles Caulier
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-devel/attachments/20180121/89412cea/attachment.html>
More information about the Digikam-devel
mailing list