[Digikam-devel] [Bug 129523] New: editing images in other programs (e.g.: gimp)

------- 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=129523         
           Summary: editing images in other programs (e.g.: gimp)
           Product: digikam
           Version: unspecified
          Platform: unspecified
        OS/Version: other
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: Image Editor
        AssignedTo: digikam-devel kde org
        ReportedBy: bluedrago web de


Version:           0.9.0-svn 2006-06-20 (using KDE 0.9.0-svn 2006-06-20)
Installed from:    KDE 3.5.3
OS:                Search

There should be a feature (after 0.9 release) to edit images in other programs than digikam, without loosing any of the important informations for the database, like date,exif,iptc,tags etc.
It could be part of somekind of versioning system (look at f-spot, bibble etc. - both can be tested free with f-spot even being open source, and both offer a versioning system for the images)
It could/should work like this:
-> when editing in another program not supporting the database stuff of digikam, it gets first copied to a temporary file
-> that temporary file is then opened in the other program (like gimp, or anything else)
-> digikam shows a question dialog "is the editing finished?" which offers "yes, copy it back" and "cancel"(which deletes the temporary file)
-> if "yes" is chosen, digikam will copy the image back with another name like DSC_xxxx_2.jpg (then maybe a new "version" of the image) and add the tags,date,exif,iptc informations which it should definately have, as it is valueable for the database
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Heiner Lamprecht]

On Tuesday 20 June 2006 23:49, Dennis Gnad wrote:

>
> -> when editing in another program not supporting the database
> stuff of digikam, it gets first copied to a temporary file ->
> that temporary file is then opened in the other program (like
> gimp, or anything else)
> -> digikam shows a question dialog "is the editing finished?"
> which offers "yes, copy it back" and "cancel"(which deletes the
> temporary file)
> -> if "yes" is chosen, digikam will copy the image back with
> another name like DSC_xxxx_2.jpg (then maybe a new "version" of
> the image) and add the tags,date,exif,iptc informations which it
> should definately have, as it is valueable for the database

I think, versioning (in terms of "image X is derived from image Y")
would be very fine.  But your workflow seems to be too difficult.  
It should be sufficient to be able to copy meta data from one image
to an other, either in terms of only adding missing fields, or
overwriting existing as well.


    Heiner

--
    heiner at heiner-lamprecht dot net    GnuPG - Key: 9859E373
  Fingerprint:  3770 7947 F917 94EF 8717 BADB 0139 7554 9859 E373
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Heiner Lamprecht]

------- 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=129523         




------- Additional Comments From heiner heiner-lamprecht net  2006-06-21 21:51 -------
On Tuesday 20 June 2006 23:49, Dennis Gnad wrote:

>
> -> when editing in another program not supporting the database
> stuff of digikam, it gets first copied to a temporary file ->
> that temporary file is then opened in the other program (like
> gimp, or anything else)
> -> digikam shows a question dialog "is the editing finished?"
> which offers "yes, copy it back" and "cancel"(which deletes the
> temporary file)
> -> if "yes" is chosen, digikam will copy the image back with
> another name like DSC_xxxx_2.jpg (then maybe a new "version" of
> the image) and add the tags,date,exif,iptc informations which it
> should definately have, as it is valueable for the database

I think, versioning (in terms of "image X is derived from image Y")
would be very fine.  But your workflow seems to be too difficult.  
It should be sufficient to be able to copy meta data from one image
to an other, either in terms of only adding missing fields, or
overwriting existing as well.


    Heiner
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier]

------- 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=129523         




------- Additional Comments From caulier.gilles free fr  2006-06-21 22:03 -------
Just a remark : a program like Gimp witch support like an hell metadata is a same for a photograph (:=)))

Gilles
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

------- 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=129523         




------- Additional Comments From bluedrago web de  2006-06-21 22:18 -------
> I think, versioning (in terms of "image X is derived from image Y")
> would be very fine.  But your workflow seems to be too difficult.  
> It should be sufficient to be able to copy meta data from one image
> to an other, either in terms of only adding missing fields, or
> overwriting existing as well.

Yeah to be able to copy metadata and stuff would be really helpful too. (and removing metadata, because on some cameras, if you use a manual lens, it saves wrong exif information (f1, 0mm etc.)

But I was talking about how other programs could be used on the images in digikam in a little bit easier way, so you don't have to separately copy the metadata by hand afterwards, and you can't forget to do it.

I anyway wasn't talking about how the versioning system could work, I don't exactly have a clue, but your idea seems really interesting, so you could have like a tree view that shows images, and new images which are made from the original? That sounds nice! Good idea!
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Heiner Lamprecht]

------- 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=129523         




------- Additional Comments From heiner heiner-lamprecht net  2006-06-21 22:33 -------
On Wednesday 21 June 2006 22:18, Dennis Gnad wrote:
>
> But I was talking about how other programs could be used on the
> images in digikam in a little bit easier way, so you don't have
> to separately copy the metadata by hand afterwards, and you can't
> forget to do it.


Well, I fear, it would be difficult to monitor, wether the external
program is still running.  And what happens, when you close digikam
in the meanwhile?

> I anyway wasn't talking about how the versioning system could
> work, I don't exactly have a clue, but your idea seems really
> interesting, so you could have like a tree view that shows
> images, and new images which are made from the original? That
> sounds nice! Good idea!


Yes, something like this.  I don't know, how easy it would be, but I
can imagine, that such a genealogy of images would be really cool.  
I often have different versions of an image.  The original file, a
somehow enhanced image, an other one cropped and resized for the
web, one printed, ...


    Heiner
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

------- 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=129523         




------- Additional Comments From bluedrago web de  2006-06-22 15:38 -------
> Well, I fear, it would be difficult to monitor, wether the external
> program is still running.  And what happens, when you close digikam
> in the meanwhile?

It doesn't has to be monitored if the external program is running or not. Digikam will offer you a dialog.
And, if digikam is closed, the image stays at it's place (somewhere in the homedir) and digikam will ask to import it again, at the next time it starts up, it then would have to save which picture was the original one it came from

> I often have different versions of an image.  The original file, a
> somehow enhanced image, an other one cropped and resized for the
> web, one printed, ...

Yeah, me too! And sometimes even a subdirectory which has batch-process-scaled images..

--

Maybe all that stuff with external programs doesnt has to be done, when the picture can be added as a "sub-picture" of another, and then will maybe also get the same date,exif,etc. from the picture it belongs to?
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel