[OctDev] Re: [Octave-cvsupdate] octave-forge/main/image imread.m,1.11,1.12 imwrite.m,1.8,1.9

[Andy A. <ax...@gm...>]

St=E9fan,

That sounds like a good idea. On the other hand, a better implementation
would be to write an oct file  to link to the imagemagick libraries directl=
y.

After that, the only reason to have jpgread etc is for users that don't hav=
e
libmagick.a.

What do you think?

Andy

On 7/24/05, Stefan van der Walt <st...@su...> wrote:
> Last time I checked, the pipes implementation was much slower than the
> file approach for large images.  Can you verify whether this is still
> the case?
>=20
> I have made some fixes to pngread and jpegread, which I will submit
> soon.  Then, we can use those functions in imread.m to load JPGs and
> PNGs, but revert to ImageMagick otherwise.
>=20
> Regards
> St=E9fan
>=20
> On Thu, Jul 21, 2005 at 04:03:08PM +0000, andy adler wrote:
> > Update of /cvsroot/octave/octave-forge/main/image
> > In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv22457/main/image
> >
> > Modified Files:
> >       imread.m imwrite.m
> > Log Message:
> > Improve error messages and use pipes
> >
> > Index: imread.m
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > RCS file: /cvsroot/octave/octave-forge/main/image/imread.m,v
> > retrieving revision 1.11
> > retrieving revision 1.12
> > diff -u -d -r1.11 -r1.12
>