On Wed, 15 Dec 1999, you wrote:
> Hi,
>
> On Wed, 15 Dec 1999, Rink Springer VII wrote:
>
> > > I was wondering if ALLEGRO could be used instead of glib.
>
> Allegro is a multimedia library, while glib is a general-purpose utility
> and portability library. You'll hardly be able to replace either of them
> with the other ;-)
>
> > > I'm
> > > not sure what it would need to do (ALLEGRO that is), and I'm
> > > not too sure how we should implement the connection between
> > > the two. I'm pretty sure that glib and ALLEGRO would not
> > > follow the same function interface, and I'm really sure that
> > > there are huge differences between the two.
> > Well, I figure it'd be best to either write our own graphics library (which is
> > relatively easy to do, since 320x200x16 is not hard to do),
>
> I'd recommend using 320x200x256, and not permanently limiting youself to
> that mode (the fabled 0.3 release series may one day provide
> resolutions than the classic 320x200 pixels).
Yup, that was my opinion as well... I just said 320x200x16 because that is the
resolutions SCI uses (in the old 16 color games). Of course we'll use
320x200x256!
>
> > or use Allegro.
> > Allegro has around all library functions we need...
Yes, but I *prefer* we use our own library. Just for the neatness... we only
need some drawing code and input stuff... nothing real.
>
> I haven't found any handling of sound events, though; you may need to
> either provide your own sound server or hack the Allegro sound system
> accordingly. IIRC the Allegro license is somewhere along the lines of the
> BSD/X licenses, with several non-legally-binding "encouragements", so this
> shouldn't be a problem.
Allegro is now under GNU, so we can hack it in any way we need (and we need!).
But, sound code isn't a priority right now (at least, not mine ;-)
I'll try to do some porting on Friday...
>
> llap,
> Christoph
Rink
