Message-ID:	<c=GB%a=_%p=Indigo_Active_Vi%l=CRIANLARICH-970304103505Z-28@crianlarich.Indigo>
From:	Robert Humphris <r DOT humphris AT indigo-avs DOT com>
To:	"'djGpp list'" <djgpp AT delorie DOT com>,
	"'billc AT blackmagic DOT tait DOT co DOT nz'"
	<billc AT blackmagic DOT tait DOT co DOT nz>,
	"'leathm AT solwarra DOT gbrmpa DOT gov DOT au'"
	<leathm AT solwarra DOT gbrmpa DOT gov DOT au>,
	"'fighteer AT cs DOT com'"
	<fighteer AT cs DOT com>
Subject:	OpenGL ----> Allegro
Date:	Tue, 4 Mar 1997 10:35:05 -0000
Encoding:	19 TEXT

You are all right, and rightly so! 
OpenGL would work well with Allegro, as I don't believe that OpenGL has
the power of sound, timing, and
various device drivers.

The question is should it sit as an API on top of Allegro, be
incorporated into Allegro, or simply use
Allegro functionality and exist as a separate module?  Would it simply
be a case of writing a set of
macros that allow OpenGL calls to be translated directly to Allegro
statements?

Come to think of it, what has OpenGL got that Allegro hasn't? Should we
not try to implement these features
in Allegro making it more powerful still?

What do you think?

Rob Humphris

- Raw text -