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

[Jens B.Benecke]

------- 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 jens-bugs.kde.org spamfreemail de  2005-09-04 18:16 -------
Am Sonntag, 4. September 2005 12:41 schrieb Thorsten Schnebeck:

> to 1)
> This is noble but hard to implement. You need versioning, you have to
> define whats an original. Only a e.g. RAW-file or also other images in
> the process chain?


Again: JUST the FIRST image. No others. Everything else is too complicated.

What is an "original"? Simple: An original is an image that has no 
equivalent in ".digikamoriginals". Where "equivalent" can e.g. be 
md5sum(filepath_relative_to_album_root) to ensure uniqueness.

> One way to work this way is that there is maximum 
> only one working copy of every image in digiKams file tree. This way you
> can use the "revert"-command not only during one IE session but also in


What's an "IE" session?

> albumview on every "open"-type command. And you need a new explicit
> "drop original" command making the workimage the new original. Of course
> the albumview shows only the working copy and may a different frame
> color or RMB->"open original" indicates that there is still an original
> image behind. This concept could work but needs modification on how
> images are managed for sure to the database level!


I'm not sure this is the case.  The original images do not need to be 
included in the Digikam database and I would not want them to be shown (by 
default, anyway).

What would be needed is:

- check for original on modifications (see above)
- if none exists, save one before saving modifications
- if one exists, provide three context menus like
	Original -> Revert / Delete / Open

My additional wish would be, to be able to combine several pics to be the 
original of one. So I can save panoramas that I glued together and mark 
all seperat images as "original" and they vanish in the originals folder. 
But this can wait and would really need a DB change. ;)

> to 2) This is my concept. I want to change an image with the IE and
> external programs. I know digikam can not take care of changes I did in
> external programs but it should take care on anything I do in the IE.


Yes! Well, actually it should be able to watch the album tree via FAM and 
when a file gets opened for read-write, it could automatically open it for 
read-only, so that it keeps the current version. When the file gets 
changed, Digikam could automagically save the old copy. But I guess that's 
quite a bit of work.

> Today you can open an image in the IE resize and click on "save". And
> now there has to come a warning, a reminder or a notice. And this does


Yes, absolutely!