Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!ucsd!sdcc6!sdcc4!ln63wkp
From: ln63wkp@sdcc4.ucsd.edu (The Priss)
Newsgroups: comp.sys.amiga
Subject: Re: HAM-E not IFF??
Message-ID: <6399@sdcc6.ucsd.edu>
Date: 23 Jan 90 07:19:21 GMT
References: <00363@sarek.UUCP> <4710008@hpfcdq.HP.COM>
Sender: news@sdcc6.ucsd.edu
Organization: University of California, San Diego
Lines: 20

In article <4710008@hpfcdq.HP.COM> olsen@hpfcdq.HP.COM (John Olsen) writes:
>How about removing the IFF/non-IFF debate entirely by making programs read
>24 bit/pixel files (already standard) and write HAM-E into memory.  When you
>save the picture, write it back out as a 24 bit/pixel file again.  Any 
>program that can handle 24 bit/pixel can then chew on the image without
>caring a single whit whether the owner wants to display it on a custom frame
>buffer or a Black Belt box.
>Comments? Flames? Money?


Yeah that would be nice except that 24 bit files can get quite
large.  I like the idea of storing an image at it's maximum
resolution for future generations, but, you can only store so many
huge 24 bit files in a small 40Mb HD (like mine).  Besides, the
conversion step may be slow and that effect you want to avoid when
running slideshows, etc.

                                            -Viet
                                               vho@ucsd.edu
Please don't flame me!:-(