[OctDev] jpgread changed

[Teemu I. <tpi...@pc...>]

On 10/12/05, Stefan van der Walt <st...@su...> wrote:
> On Wed, Oct 12, 2005 at 07:32:23PM +0300, Teemu Ikonen wrote:
> > I have a rewrite of imread as an oct-file binding to libmagick++ in
> > the works. AFAIK Imagemagick supports all of the formats of the
> > current imread implementation or more and I found that reading some
> > formats to octave is 2 orders of magnitude faster with imagemagick.
> Is the libmagick++ API stable?  We experimented with it a while ago,
> and had problems over different versions.

I have no idea about the stability of the API, other than that Debian
seems to be having some sort of library transition going on with it at
the moment.

> What I don't like about that solution is that we'll be needing a lot
> of extra development headers, many of which we'll never use.  So we
> should probably look into making use of more ImageMagick functionality
> in other parts of the image toolbox as well.

We will have to use the library dependencies if we want to support
loading of large number of formats and IMHO we should. The solution to
octave-forge having dependencies to half of the world is to devise a
decent module system to Octave and split octave-forge to smaller
pieces.

Teemu