comp.lang.ada
 help / color / mirror / Atom feed
From: Gautier write-only <gautier_niouzes@hotmail.com>
Subject: Re: A generic image decoder - specification design
Date: Sun, 2 May 2010 08:09:35 -0700 (PDT)
Date: 2010-05-02T08:09:35-07:00	[thread overview]
Message-ID: <90a9fdb6-7a1c-44a5-a6ce-1288de7561c5@o8g2000yqo.googlegroups.com> (raw)
In-Reply-To: 8f304$4bdd43b6$541ed605$26008@cache6.tilbu1.nb.home.nl

On May 2, 11:19 am, Andre <avsa...@hotmail.com> wrote:

> The first question which comes up in mind is: where do you want to use
> it for?
> Is it an initial step for your Ada based browser?

Many things, from image manipulation without display, loading of
textures for GL (there it would replace the "input" part of the GL.IO
provided with GLOBE_3D), display into a rectangle of a GUI system and
an in-memory cache (good guess: for a browser :-) ),...

> The 2nd question is more basic, are you write the load image functions
> in Ada or use bindings to existing libraries (like the JPEG one)?

The whole would be in Ada. The code already exists for GIF, BMP, TGA,
in different places. The decompression for PNG can be taken from
UnZip.Decompress. JPEG is a bit trickier.
There are "Pascal" sources that could be used, perhaps.

> Basically all pixel based images are a block of memory. The one which
> are 8 bit based use normally a Palette (like GIF and 8-bit BMP). The
> full color versions (JPEG, 24-bit BMP) use 3 or 4 byte per pixel (4th
> one is in general the alpha channel) in a memory map. So that can easily
> be modeled.
> If it is for a browser, you can forget about the 1-, 2- and 4-bit images.
>
> So how will be your real image data be modeled?
> Do you plan to just use a 24-bit with alpha channel format and convert
> lower grade images (like GIF) into this format?
> Or do you want to represent the different image types also in you data
> model?

The color model is 24-bit. Palettes will be decoded.
The transparent pixels in GIF will have alpha=Opacity_range'First and
the others will have Opacity_range'Last.
All the rest (basically, the choice of the memory model, and what to
do with transparency) is left to the user.
For instance GL.IO will keep its model: a data buffer, which is sent
to GL via Insert_into_GL.
But decoded pixels might be even directly sent to a "screen" or a GUI
object if it makes sense (e.g when decoding an interlaced PNG to a
visible image on a Web page), without any Ada storage of the image.

> just some feedback,
> André

Thanks for it!
Gautier



  parent reply	other threads:[~2010-05-02 15:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-01 17:03 A generic image decoder - specification design Gautier write-only
2010-05-01 20:30 ` Gautier write-only
2010-05-02  9:19   ` Andre
2010-05-02 10:48     ` RasikaSrinivasan@gmail.com
2010-05-02 15:09     ` Gautier write-only [this message]
2010-05-02 15:21       ` Dmitry A. Kazakov
2010-05-02 19:21         ` Gautier write-only
2010-05-02 11:45 ` brian
2010-05-02 15:15   ` Gautier write-only
2010-05-02 19:24   ` Gautier write-only
2010-05-02 22:07     ` Brian Drummond
2010-05-02 23:01       ` tmoran
2010-05-03 12:18         ` Gautier write-only
2010-05-05 21:07 ` A generic image decoder - first preview! Gautier write-only
2010-05-24 20:51 ` A generic image decoder - specification design Stephen Sangwine
2010-05-24 21:42   ` Gautier write-only
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox