Re: merging imread and imwrite

[John W. Eaton]

On 29-Jan-2008, Søren Hauberg wrote:

| > Also, is there some other graphics library that we could wrap to
| > handle reading and writing image files that might be better, or is
| > ImageMagick a good choice?
| I don't know if ImageMagick still insists on breaking their API on a
| regular basis, but some time ago they did. If this is an issue then
| GraphicsMagick might be a better choice (it's a fork of ImageMagick that
| attempts to keep their API stable).

Would using the GraphicsMagick++ library be a good choice?  Will that
cause trouble for Windows or OS X?  My goal is to simplify the
imread/imwrite functions.  Ideally, it seems that those functions
should be very simple, and we wouldn't need to have special cases for
the actual reading or writing various image types, though we would
need some logic to properly convert given image types/bitdepths to the
right data type for compatibility with Matlab's imread function.
Perhaps almost all of that could be handled in a .m file.

jwe