Re: [Gimp-developer] GIMP Video Menu (GAP)

2002-02-04 Thread Sven Neumann

Hi,

wolfgang hofer [EMAIL PROTECTED] writes:

 Where can I get the latest
 Version of the Subdirectory 
 plug-ins/gap  ?
 
 - I have gimp-1.2.2 tarball
 - I have gimp-1.3.2 tarball
   that does not contain plug-ins/gap.
 - I have seen the CangeLog of 1.3.2
   and there were changes affecting gap
   after the 1.2.2 release.
 - I have heared, that gap
   does not compile in the 1.3 branch.
 - I want to try to fix the problems,
   and change to 1.3 , 1.4 API.
 - I have NO internet on my linuxbox 
   and cannot use CVS.
   (download is possible once or twice a week 
on a foreign win98 PC)
 - I am the author of gap
 
 Who can help ?

I can easily set up nightly CVS snapshots for you.  The question is,
do I put them up only for you or is there general interest for CVS
snapshots? I'd probably put them on up on ftp.gimp.org then.


Salut, Sven

___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer



[Gimp-developer] Re: cvs gimp segfault in gimp_tool_pop_status

2002-02-04 Thread Michael Natterer

David Odin [EMAIL PROTECTED] writes:

Hi,
 
 I've just discovered a segfault bug in the current HEAD CVS gimp.
 To activate the bug: start gimp, select some rectangle area, use the
 move tool, bang!

Oops :) I thought the tool_info's name was a nice unique string for
identifying the tool, but the edit_selection_tool has no tool_info :(

Will check in a fix with my next commit.

thanks,
--Mitch
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer



Re: [Gimp-developer] EXIF information in JPEG files

2002-02-04 Thread Branko Collin

On 4 Feb 2002, at 14:08, Lutz Müller wrote:

 I have written an EXIF library in plain C (libexif) and some GTK+
 widgets for displaying and modifying EXIF data (libexif-gtk). Both
 are available on http://libexif.sourceforge.net. I use them to display
 EXIF tags in gphoto2 (command-line frontend) and gtkam (GTK+ GUI).

 However, when loading images from a digital camera directly into gimp
 and letting GIMP save the images (i.e. as JPEG files), all EXIF
 information gets lost. In addition, right now, gimp doesn't offer
 access to EXIF information when loading JPEG files.

 How do I go about adding EXIF support to gimp? Should I distribute a
 loader for JPEG files that replaces the current one? Submit a patch to
 gimp's JPEG loader and configure.in to --enable-exif if libexif(-gtk)
 is installed?

Dave Neary and Raphael Quinet started work on EXIF for the GIMP. I
suggest you contact them. Their discussion can be found here:

http://lists.xcf.berkeley.edu/lists/gimp-developer/2001-
December/006057.html

 In any case, how do I save per-image (not per-loader) EXIF data?

I believe the idea is that meta-information gets stored in GIMP's
parasites, and that the loaders/savers get adapted to do the
conversion back and forth (IANAC).

--
branko collin
[EMAIL PROTECTED]
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer



Re: [Gimp-developer] EXIF information in JPEG files

2002-02-04 Thread Dave Neary


Hi Lutz,

 I have written an EXIF library in plain C (libexif) and some GTK+
 widgets for displaying and modifying EXIF data (libexif-gtk). Both
are
 available on http://libexif.sourceforge.net. I use them to display
EXIF
 tags in gphoto2 (command-line frontend) and gtkam (GTK+ GUI).

Thereare a couple of other libraries which do pretty much the same
thing -
see the relevant bug numbers in bugzilla (not sure what they are right
now).
I haven't had a chance to look closely at this, but it looks good.

 However, when loading images from a digital camera directly into
gimp
 and letting GIMP save the images (i.e. as JPEG files), all EXIF
 information gets lost. In addition, right now, gimp doesn't offer
access
 to EXIF information when loading JPEG files.

Yup. We use a straight call to libjpeg's header parser, which doesn't
know
anything about exif. A couple of people (myself and Raphael Quinet)
were
looking at this with a view to adding support in 1.3 at least about a
month
and a half ago. Then I moved to France, and that got put on the back
burner,
and my computer's still in storage. The last I had done was a very
simple
hack which replaces our call to the header reader with a call which
read exif
information. The next step would have been to specify how that
information
would be passed over and back between the main gimp and the jpeg
plug-in.
There was some discussion on this, and it was agreed by everyone
(eventually) that parasites were the way to go. So all we need to do
is define
what information would be available in the exif parasite, and how to
get at it.
I spent a bit of time at this writing up a short RFC, but it was
pretty scattered,
and never got finished/posted to the list.

 How do I go about adding EXIF support to gimp? Should I distribute a
 loader for JPEG files that replaces the current one? Submit a patch
to
 gimp's JPEG loader and configure.in to --enable-exif if
libexif(-gtk) is
 installed?

If you write a wee report which says what exif information you get out
of the file,
and read up on parasites (which is about where I was at 6 weeks ago),
post a
mail to the list with reccommendations, and then code whatever comes
out of
the reccommendations. Until my computer comes out of storage (15th of
February)
I'll be useless to you, but there are otehrs who were interested in
doing this too.
There was a proposal before to have an exif data editor (or even a
parasite editor)
as well, but I reckon the first step is getting the exif stuff read
into some well-defined
structure, and getting it written out to files in the same proper
structure without
destroying it. If we can do that, a generic parasite editor can handle
the editing of
the metadata.

 In any case, how do I save per-image (not per-loader) EXIF data?

I'm not sure what you mean by this...

 Lutz

Hope this helps,
Dave.


___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer



Re: [Gimp-developer] EXIF information in JPEG files

2002-02-04 Thread Lutz Müller

On Mon, 2002-02-04 at 14:29, Dave Neary wrote:
 Thereare a couple of other libraries which do pretty much the same
 thing -
 see the relevant bug numbers in bugzilla (not sure what they are right
 now).
 I haven't had a chance to look closely at this, but it looks good.

There is python stuff, a C++ library, lots of programs, but no plain C
library. Plus, everything out there is designed for _extracting_ EXIF
data, not _editing_ it. This is why I designed libexif(-gtk).

 Yup. We use a straight call to libjpeg's header parser, which doesn't
 know
 anything about exif. A couple of people (myself and Raphael Quinet)
 were
 looking at this with a view to adding support in 1.3 at least about a
 month
 and a half ago.

So I am the third person looking at it :-)

I just don't know how to handle the dependency on libexif(-gtk). You
know, libexif itself is quite small and could be included in gimp
(although I'd keep it separately), but libexif-gtk is getting bigger and
bigger as more widgets are added. Therefore my question: Is it ok to
introduce a (conditional --enable-exif) dependency on libexif(-gtk) for
gimp?

 The last I had done was a very
 simple
 hack which replaces our call to the header reader with a call which
 read exif
 information.

This is now a one-line call to libexif (exif_data_new_from_data()).

 The next step would have been to specify how that
 information
 would be passed over and back between the main gimp and the jpeg
 plug-in.
 There was some discussion on this, and it was agreed by everyone
 (eventually) that parasites were the way to go.

Ok, I'll look into this.

 There was a proposal before to have an exif data editor

This is libexif-gtk - just call gtk_exif_browser_new () and you've got
the editor...

 (or even a
 parasite editor)
 as well, but I reckon the first step is getting the exif stuff read
 into some well-defined
 structure, 

Already there in libexif.

 and getting it written out to files in the same proper
 structure without
 destroying it.

Not yet done. I'll try.

Lutz
-- 
+--+  \|||/
| Lutz Müller+49 (7156) 34837  |  (o o)
|  +---ooO-(_)-Ooo---+
| Hans-Sachs-Strasse 5   |
| 71254 Ditzingenhttp://www.topfrose.de  |
| Germany[EMAIL PROTECTED]  |
++



signature.asc
Description: This is a digitally signed message part


Re: [Gimp-developer] EXIF information in JPEG files

2002-02-04 Thread Sven Neumann

Hi,

Lutz Müller [EMAIL PROTECTED] writes:

 So I am the third person looking at it :-)
 
 I just don't know how to handle the dependency on libexif(-gtk). You
 know, libexif itself is quite small and could be included in gimp
 (although I'd keep it separately), but libexif-gtk is getting bigger and
 bigger as more widgets are added. Therefore my question: Is it ok to
 introduce a (conditional --enable-exif) dependency on libexif(-gtk) for
 gimp?

if it solves our problems and works for non-JPEG images too, I don't
see any problem in adding such a dependency to gimp-1.3.


Salut, Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer



Re: [Gimp-developer] EXIF information in JPEG files

2002-02-04 Thread Raphael Quinet

On Mon, 04 Feb 2002, Lutz Müller wrote:
  On Mon, 2002-02-04 at 15:04, Sven Neumann wrote:
  if it solves our problems and works for non-JPEG images too, I don't
  see any problem in adding such a dependency to gimp-1.3.
 
  EXIF information is specific to JPEG files. Therefore, editing and
  storing EXIF information make sense with JPEG images only. Sure, you
  could try to save/hide/convert it in other image formats, but this is
  not the purpose of the EXIF specification.

EXIF is specific to JPEG files, but you find almost the same
information in the TIFF/EP format.  So we should try to have a generic
solution for the GIMP, that is not limited to EXIF only.  If you look
at bug #56443 and have a look at the proposal for adding EXIF support
to the PNG file format (http://pmt.sourceforge.net/exif/index.html),
you will see a long table that describes how the individual fields can
be mapped from one file format to the other.

That's why I wrote in my previous mail that all data should be saved
in GIMP parasites, because that would allow each file plug-in to
import/export the parts that are appropriate and discard or convert
the rest.  So we should be able to have something like this:
   Load JPEG/EXIF file - GIMP parasites - Save TIFF/EP file

-Raphael


___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer



Re: [Gimp-developer] EXIF information in JPEG files

2002-02-04 Thread Lutz Müller

On Mon, 2002-02-04 at 14:29, Dave Neary wrote:
(...)

Just so that you get an impression of libexif-gtk, I put up a screenshot
of gexif, a frontend to libexif-gtk, on

http://helena.bawue.de:8080/~lutz/projects/libexif/index.html

I imagine this dialog being accessible either through some menu or
through the JPEG-save-dialog (additional tabs). However, I first need to
get either a larger disk for my laptop or a new computer in order to be
able to work on this - don't have a gtk  1.2.x installation here.

Lutz

PS: It would be nice if this mailing list program could automatically cc
replies to anyone sending mails to this list while not being subscribed
(like me).
-- 
+--+  \|||/
| Lutz Müller+49 (7156) 34837  |  (o o)
|  +---ooO-(_)-Ooo---+
| Hans-Sachs-Strasse 5   |
| 71254 Ditzingenhttp://www.topfrose.de  |
| Germany[EMAIL PROTECTED]  |
++



signature.asc
Description: This is a digitally signed message part