[Digikam-devel] [Bug 103350] its too easy to save images

[Gilles Schintgen]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=103350         




------- Additional Comments From gilles vonet lu  2005-07-28 14:08 -------
The more I want to actually fix my images, the more frustrated I become by the current digikam behavior. There's no way I'm going to overwrite my original pics. Unfortunately digikam doesn't handle backup copies at all. Right now it's a complete nightmare to have a backup copy (which obviously should have the same comments and tags as the modified image). Currently, I always make a copy of my originial pic. (This copies metadata too.) Then I modify the copy. But there's still the problem of keeping the metadata in sync.

The only way digikam's image editor can become useful is proper version handling by digikam. Here's what I'd like to see:
- digikam never ever touches the original image.
- modifications are done on a (single) copy.
- both images are kept in sync. (metadata)
- they are also moved or copied together as one logical picture.
- by default digikam only shows the retouched copies
- optionally it also shows the original
- the modified image is given a special name (like "origname_modified.jpeg")
  and stored in the same folder as the original.

This is somewhat similar to Apple's iphoto. IIRC iphoto never asks to save the modifications (which is bad), but always keeps a backup copy and allows to revert to the original state. IMO completely hiding the original is a bad idea. Hence my proposal above.