[Digikam-devel] [Bug 142056] Save changes of image modifications with Versioning.

[Dotan Cohen]

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





--- Comment #45 from Dotan Cohen <kde-3 dotancohen com>  2009-06-16 10:37:21 ---
> I still don't see how that is in any way equivalent. If the list is
> flat and "most versions" started off from the original image, then
> what about the other versions, how can I tell where they came from?
> With more than one "leaf" image, which leaf or leaves should be
> displayed?

The last revision would be the version shown, unless the user selects a
different revision.


> Maybe I'm over-thinking the whole thing, because I'm used to tracing
> the history of source-code changes in trees in my day job and in my
> free time I tend to make lots of different versions of key photos with
> different orientations, crop areas and aspect ratios, so revision control
> (like with RCS) with branching would be second nature to me.

Yes, I suspect that you are overthinking it! Existing photo managers that
support versioning just have a list of versions in the order that they were
finished, without regard to how they started off. In reality, if the user is
making so many versions of a photo that he needs revision control, then
managing them in Digikam as versions of a single photo is not the proper
workflow. The intention of versioning in Digikam is to let the user make some
small touchups (correct redeye, straighten photos) and save them without
erasing the original image. It does not need to be overcomplicatd to revision
control.

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