Hi,
William Skaggs [EMAIL PROTECTED] writes:
Okay, following up on earlier discussion: I think I have a
reasonable way of dealing with the jpeg-exif stuff until Raphael's
metadata code arrives.
Sorry, but before I continue reading, why is Raphaels' metadata code
not available? You certainly
Sven wrote:
Sorry, but before I continue reading, why is Raphaels' metadata code
not available? You certainly wrote him a mail asking for it, didn't
you? So why is he holding the code back? Does it even make sense to
continue discussing this w/o Raphael?
The code is available from
Hi,
William Skaggs [EMAIL PROTECTED] writes:
The code is available from Raphael's web page, but it isn't in CVS,
and it's up to Raphael when to put it there.
AFAIK the code available there is somewhat outdated and the API might
have changed.
And yes, it makes sense to continue discussing
Hi,
William Skaggs [EMAIL PROTECTED] writes:
The interface between the jpeg plug-in and the metadata system, so
far as exif is concerned, would consist of two functions,
gimp_metadata_store_exif() -- which translates the exif into XMP and
adds it to the metadata parasite -- and
Me:
(Raphael's plan has them implemented as plug-ins, but I think that's too
awkward.)
Sven:
What is akward about it?
Passing, say, an ExifData struct to a plug-in is awkward. Calling a function
and giving it a pointer is simpler, and much faster too. And then there's
all the extra
I came across this nice example of decay on a sign a few days ago
(http://pages.quicksilver.net.nz/pepe/no.jpg), and thought it would be nice if a
plugin would be able to generate such random patterns automatically.
Does anyone knows about such a plugin, or anything close? Can someone suggest
the
