[Digikam-devel] [Bug 203593] New: initial workflow, selecting images to delete

lertimir at centrum.cz lertimir at centrum.cz
Wed Aug 12 17:33:29 BST 2009


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

           Summary: initial workflow, selecting images to delete
           Product: digikam
           Version: 1.0.0
          Platform: Compiled Sources
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: digikam-devel at kde.org
        ReportedBy: lertimir at centrum.cz


Version:           1.0.0 (using Devel)
OS:                Linux
Installed from:    Compiled sources

I am writing this as a photographer not a computer specialist. Every good
course start with "throw your bad photos". Which means select good ones and
delete bad ones. Digikam has little support for this initial workflow step. It
could be from 20% of bad photograps, when shooting landscape, architecture and
other situation with plenty of time for prepare to some 95% - 98%, when
shooting sports, parties, concerts, children and other action. Select 50
promising photos out of 1000 is tedious process with digikam.

I propose:
1. Fullscreen in view mode should be able to be really fullscreen, without
borders, line of thumbnails, menu etc. Similar as in edit mode, but quicker
when moving through images. 1 sec slower
2. this fullscreen mode should have switching between "zoom in/full image"
preferably on one key like on/off switch, similarly as window can switch
between "normal/maximize" . And the zoom position should be maintained for next
image. This is important feature as it allow compare images one over another.
Your "light table" allow compare images side by side, this could compare in one
place and more with a fullscreen feeling. 
3. Marking images. I mean on/off switch for temporary selecting. And then
choose action, i.e. move, copy, delete, or this list for batch processing.
Tagging is not practical, one need select tag, which slows selecting, and
removing tag in the and slows too. Marking should switch with pressing one key.
And select from system with Ctrl+click Shift+click is very very vulnerable. One
wrong click and all selection is out.
4. Speed. I don't say that digikam is slow. But if it will pass through line of
images 3 times quicker it save me 30% of time. A solution could be prepare more
images for viewing in advance. Not only next one, but 3,5,8 images. In every
situation is clear for each image which is next, so it needs only memory, and
memory is now cheap. It would be great to have some options in "Configure
digikam" to grant it some amount of memory i.e. 2GB, and you could use it to
speed the work. It could be similar as in modern CPUs, when CPU does jump it
compute both branches before knows where to go.

Thank you for your attention and I am sorry for my english.

lertimir

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



More information about the Digikam-devel mailing list