Bug 235572 - FACTORING : Add a new BQM tool to export on remote computer (as Web services)
Summary: FACTORING : Add a new BQM tool to export on remote computer (as Web services)
Status: REPORTED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-Bqm-WishForNewTools (show other bugs)
Version: 1.3.0
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
: 207907 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-04-27 21:04 UTC by Allan Andersen
Modified: 2023-12-01 14:05 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Allan Andersen 2010-04-27 21:04:49 UTC
Version:            (using KDE 4.3.5)
OS:                Linux
Installed from:    openSUSE RPMs

I use digiKam for managing my pictures but also to upload to my web photo album.

One feature which really would help choosing the right pictures is when browsing (like viewing in full screen) is possible to add the picture to 'Queue for export to XXX'.

Right now I have to choose 2-5 pictures at the time, upload these and then continue down the album. With this feature it would be possible view all pictures and mark picture by picture and upload at the end.

Thanks to the digiKam guys and the KDE team.
Comment 1 Johannes Wienke 2010-04-28 11:42:29 UTC
Generally adding all export tools to the BQM sounds like a good idea.
Comment 2 Jens Mueller 2010-04-28 21:15:35 UTC
We have also wish #196894, I suggest to add both to BQM output selection, so we will get:

Albums
 +Album1
 +Album2
Filesystem
 +/root
WebExport
 +Plugin1
 +Plugin2

What do you think about?

Regards, Jens
Comment 3 Allan Andersen 2010-04-28 21:58:28 UTC
Sounds like very a good idea Johannes and Jens.
Comment 4 caulier.gilles 2010-04-29 10:52:31 UTC
This is what i plan to do at next coding sprint. This will require à lots of work everywhere, and i will need help to patch digiKam; libkipi , and kipi-plugins...

Gilles Caulier
Comment 5 Allan Andersen 2010-04-29 11:01:46 UTC
Sounds great Gilles - I'm not a coder but let me know if I can help in any way.
Comment 6 Tom Vincent 2012-05-25 15:57:48 UTC
What's the status on this?

I'm looking for a way to mass upload/export to different services (i.e. upload to Flickr, Picasa, 500px etc. in one click). Adding this functionality into the batch queue would be useful.
Comment 7 caulier.gilles 2014-09-02 07:25:12 UTC
*** Bug 207907 has been marked as a duplicate of this bug. ***
Comment 8 caulier.gilles 2018-11-03 11:02:46 UTC
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface anymore. All tools are now located in digiKam core as well for a plan to provide a more power-full integration with Batch Queue Manager and to be able to export a workflow on a web-service.

All export tools are now available everywhere : album view, Image editor, Light table, and Showfoto. Previously, only album view from digiKam core was able to deal with export tools through libkipi.

All export tools are now located here :

https://cgit.kde.org/digikam.git/tree/core/utilities/assistants/webservices

All export tools use now a dedicated interface to communicate with the application : 

- digiKam (database) : 

https://cgit.kde.org/digikam.git/tree/core/libs/database/utils/ifaces/dbinfoiface.h

- Showfoto (files metadata) : 

https://cgit.kde.org/digikam.git/tree/core/utilities/assistants/common/dmetainfoiface.h


There is not direct use of digiKam database for compatibility with Showfoto.

We plan later to provide a dynamic loading of export tools using a plugins mechanism. This will reduce overloading of the internal core libraries. A dedicated devel branch have been created for that, but it's not yet complete:

https://cgit.kde.org/digikam.git/tree/?h=development/dplugins

But take a care, digiKam export tools as plugins will not be shared with another external application. API will still private and only shared between Showfoto and digiKam core. The experience with libkipi was bad and complex to maintain/extend in time.

Gilles Caulier