delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1996/10/24/00:42:21

From: Elliott Oti <e DOT oti AT stud DOT warande DOT ruu DOT nl>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Which graphics library is better?
Date: Wed, 23 Oct 1996 13:14:02 -0700
Organization: Academic Computer Centre Utrecht, (ACCU)
Lines: 30
Message-ID: <326E7C8A.113F@stud.warande.ruu.nl>
References: <01bbc0ce$e6776180$88015838 AT peterstb DOT usps DOT gov>
NNTP-Posting-Host: warande1078.warande.ruu.nl
Mime-Version: 1.0
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

B. Peterson wrote:
> 
> Can anyone briefly explain the differences in some of the different
> graphics libraries and which is better to use?
> Like... JLib, Allegro, etc.
> 
> Thanks
> Bruce 
Jlib : Target : multiplatform game programming
       Users  : primarily people who want the same graphics code
                to compile on Linux and Dos without changes.
       Offers : graphics primitives, blitters, palette and sprite
                functions + some extra's
       Speed  : Reasonable.
   My opinion : Use it if you really want portable code. Otherwise
                use Allegro.

Allegro : Target : DOS game programming
          Users  : people who want to code games with multiple graphics
                   resolutions, VESA support etc.
          Offers : mode 13h, tons of Mode X's, VESA 1.2 & 2.0 support,
                  some individual chipset support, graphics primitives,
                  sprites, blitters, GUI, timers, MIDI, digital sound,
                  etc etc etc. MikAlleg offers mod-player support.
          Speed  : In some cases, great.
      My Opinion : For scrolling & platform games, seek no further.
                   For 3D texture-mapped games, raycasting or heightmapping
                   it can be used but I don't advise it.           

Elliott

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019