Mail Index

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [ApacheGallery] previous code segment

Could be done, I'm looking at Image::Info::JPEG right now, and I could
squeeze it in there, but really it seems to sort of go against the process
of the Image::Info system, which seems geared at dropping out non-parsed
type info.  Would it perhaps be better to just make an Image::Digicam::*
set of modules that could be extended for each type of digital camera?  I
don't know, I'm just asking.  Gisle Aas (Image::Info::JPEG) wouldn't
happen to be on this list :)

If we made the new module, we could set it up so that the fields you
request always have the same name, so ISOSpeedRatings would always return
ISOSpeedRatings, and not just on non-Canon cameras.  I'm not working right
now, so I've got some time for a few days to write some stuff.

What do you think TE?

On Mon, 20 May 2002, Thomas Eibner wrote:

> On Mon, May 20, 2002 at 02:56:26AM -0400, Tom Allen wrote:
> >
> > my code segment will actually probably only work on G1/G2 type cameras,
> > but there's a host of other bits of info in there as well.  It's based
> > off some exif code found at .  That
> > dumps the whole bunch of Canon specific code.  I used it to compute the
> > offset from the MakerNote field.
> >
> > hope it helps
> You seem to understand how to make it work with Image::Info, would it be
> a lot of work to patch Image::Info so that it understands all the MakerNote
> fields natively? I'm sure we're not the only ones wanting more information
> than Image::Info can give us right now.
> --
>   Thomas Eibner <> DnsZone <>
>   mod_pointer <> <>
>   !(C)<>                  <>
>           Putting the HEST in .COM <>
> ---------------------------------------------------------------------
> Apache::Gallery users mailinglist.
> To unsubscribe, e-mail: [email protected]

Apache::Gallery users mailinglist.
To unsubscribe, e-mail: [email protected]