[Kde-imaging] [Bug 194811] flickr export in separate process

[Thomas Sperre]

https://bugs.kde.org/show_bug.cgi?id=194811





--- Comment #6 from Thomas Sperre <thomas sperre yahoo com>  2009-06-04 23:39:49 ---
I have been thinking about this for a few days: yes, the lock feature is a nice
addition too - but i think it is not right to make it a requirement. 

It is possible for a reasonably well disciplined user to engineer workflows
within the existing digikam software that avoids tampering with files tagged
for upload.  Also, it is nowhere near fatal to upload the wrong image to
flickr...it is just a delete and retry.

However, if it is possible to upload with flickr upload plugin without lock,
the plugin must be able to process the queue without stopping at all problems
(ie...list problems in a report window (+file?) after queue rather than stop at
every problem). If files in the queue are deleted, the upload plugin must
continue with the next file and not stopped. In other words, I am against
making the upload in separate process a dependency of the lock feature
(although it clearly will benefit from it). However, this may demand some more
work on making the upload process robust from stopping due to minor problems.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.