[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-bugs-dist
Subject: [Bug 103350] its too easy to save images
From: "Jens B.Benecke" <jens-bugs.kde.org () spamfreemail ! de>
Date: 2005-09-04 9:06:09
Message-ID: 20050904090609.5396.qmail () ktown ! kde ! org
[Download RAW message or body]
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.kde.org/show_bug.cgi?id=103350
------- Additional Comments From jens-bugs.kde.org spamfreemail de 2005-09-04 11:06 \
------- Hey,
I submitted a similar bug a while ago. (or was it just on IRC? Can't find the bug \
...)
I think this feature is really needed, but it can be kept as simple as possible. No \
need to save a complete editing history. The only thing that matters is to keep the \
original.
Suggestion:
- Let Digikam assume that pictures are not edited outside Digikam. There is no way \
for Digikam to know, and no user would expect Digikam to handle this.
- Upon calling an external editor from within Digikam, Digikam saves a backup copy of \
the file in .kde/share/apps/digikam/originals/originalfilename_md5(originalfile).extension. \
(To keep the name simple and outside the album tree, and to avoid collisions.) Or, if \
you want to keep you originals with the album, use albumpath/.digikam_originals where \
this path can be appended with some random chars (eg. ".digikam_originals_5ab3") if \
it already exists.
- When the external editor finishes, Digikam compares the backup with the original \
and if both are still identical, deletes the backup. If not, keep the backup.
- If an internal editor is called, we can just put the save_backup procedure I \
described in the internal editor's "Save" function.
- If a backup for a file exists (this can be cached in the database), provide a \
"Revert to Original" context menu item, and - perhaps - mark the image with a small \
image of a pen in one corner, so that it shows that it's been edited. The context \
menu item will just copy the original file over the current one.
Does this sound feasible?
Thanks!
Jens
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic