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

[Martin Rehn]

------- 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 martinrehn hotpop com  2005-09-06 18:27 -------
For reference, here is how the F-Spot (http://www.gnome.org/projects/f-spot/) version management works:

1) You can never edit the original image -- any initial edit creates a new "Image1234 (Modified).jpg" file.

2) The "Modified" version gets overwritten by subsequent edits, but the user can also manually choose to create new named versions.

3) Only one of the versions of an image is active -- meaning it is the one that is affected by edits and also the only one that is shown in the album view. This allows you to edit images and to preserve the originals, all while not cluttering your album. The user may select which version is to be the active one.

4) To revert to the original, just select that version to be active. (File->Version->Original). The modified version is kept. If you now edit the image again, a new version "Modified (2)" is automatically created so that the previous version ("Modified") is not overwritten.

5) The user can delete or rename a version of a file, but not the original. (Of course images can be completely deleted, but not from the version-related menu.)

In my opinion this is a very nice functionality; the user may never be aware that there is any version management going on until the day when she realizes that she just accidentally destroyed an important picture, desperately searches through the menus for a cure and to her delight finds that the original picture is sitting right there, under File->Version->Original.

An additional functionality, which should be easy to implement would be to keep track of the parent of each image version, so that revisions can be presented in a tree-like fashion.