Is there any reason why I cannot support several formats? I could keep the tga loader and add in a pgm and bmp loader, and everyone would be happy. The loader to be used would be determined by the magic number (first 4 characters) of the file. Unless distribution size and compiled size is an issue, I don't see the cruft as being as big an issue as clueless (particularly MS Windows) users scratching their heads over what is a pgm or png file. The loader code can be relegated to the very end of the source file, seperated by 20 blank lines, if readability is a concern. Sincerely, Robert Edele On Sat, 2005-02-26 at 06:48 +0100, Alexander Strasser wrote:
Trent Piepho wrote ( On Fri, Feb 25, 2005 at 06:39:32PM -0800 ):
On Fri, 25 Feb 2005, Reimar Döffinger wrote:
ppm for color + pgm for alpha. And yes, it is possible to create this with gimp (or in the worst case with tifftopnm), the other way round
Automatically with the gimp? My gimp doesn't have that option. I guess you have to extract the alpha somehow and save it separately, I'm not a gimp expert.
I know as a user I'd rather deal with one compressed png image for each bug than multiple different format uncompressed images. Keep in mind, ATSC is up to 1920x1080 resolution. It seems that with ppm+pgm files, you're only making the code a little simpler if at all, but have something that's less useful to use.
IMHO png alone is not acceptable. As long as there is no common image loading facility provided by mplayer it is best to use simple formats like ppm/pgm or tga.
Alex (beastd)
_______________________________________________ MPlayer-dev-eng mailing list MPlayer-dev-eng@mplayerhq.hu http://mplayerhq.hu/mailman/listinfo/mplayer-dev-eng