delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1997/04/15/10:49:35

From: frenchc AT cadvision DOT com (Calvin French)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: AllegroX project?
Date: Mon, 14 Apr 1997 09:28:08 GMT
Organization: CADVision Development Corp.
Lines: 57
Message-ID: <5iuapm$28n4@elmo.cadvision.com>
References: <5ina4e$1qmc AT elmo DOT cadvision DOT com> <01bc47e0$b3940540$428911d1 AT imag DOT net DOT imag DOT net> <5istrq$lq8 AT wallaby DOT aussie DOT net>
NNTP-Posting-Host: ts19ip175.cadvision.com
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

"Sly" <sly AT aussie DOT net> wrote:

>Yes it is clear.  I don't think it is even possible for DirectX to be used
>in DOS, since it is designed for, programmed for, and installed into,
>Win95.  Is it just me, or does it seem like people are really beginning to
>blur the line between Win95 and DOS programming?

The line is blurred. Originally I had proposed just using the
OEM-shipped DirectX driver, no windows at all. But someone else made
the brilliant suggestion of just allowing Allegro to support DirectX
when run from within Win95. But even ignoring this thread, the line
between Windows and DOS programming is already blurred. Remember that
even Win95 is only a thin fabric covering hardware, only "stepping in"
when it has to. It is not any kind of great interpreter, redirecting
hardware ins and outs accordingly, or any such thing. There are API
calls, however, and this is basically the difference between DOS and
Windows programming. But even a simple DOS program can make Windows
API calls (much in the same way as a simple DOS program can detect the
presence, version of Windows) without too much difficulty, but then of
course it is a Windows program, since it requires Windows. Sure, there
are other differences, but how many and where they lie definitely
blurs the line. I always see the joy of Allegro as being a possible
multi-platform game development suite; DOS, linux, Win95... So if I
write a game using Allegro (which is easier than coding for just
Windows, let alone all3) suddenly it can take advantage of DOS, linux
and Windows platforms. DOS, through the hand-crafted drivers Shawn
(and others??) have supplied with Allegro. Linux, through whatever is
planned for linux (I've never used it myself). And Win95, if we add
DirectX support.

Shawn, I would really be interested in your input on this. Can Allegro
be made into a multi-platform game lib? People (who know more than I)
seem to suggest that adding *just* DirectX support would be near
impossible, but that allowing Allegro to make Win95 DirectX API calls
when run from within Windows is doable. And I know that linux was
originally slated as a separate lib, so you'd at least have to ship 2
versions, but wouldn't it be kewlio to just have one, unified lib
which takes advantage of whatever's there? Or would this require
Allegro to be redesigned? I love Allegro because it is eloquent, it is
straight c (allowing me to design my own OO interface over it, as
robust or simple as I like... this is very important to me. Keep it
straight C. Don't try and impose your own OO implementation, please
:-) At least that's my take...) and it is not overbig. I hate
libraries that
expand into like fifty gaschmillion different directories and files.
Anyways, now I'll get off my soapbox. What do you think though, about
making one unified lib that is cross platform? Is it possible? At
least I would love to see a version that could take advantage of Win95
API calls, but at least I'm not the person to do this, and you've got
your hands full with the TrueColor stuff.

Then, we can add Mac support.

- Calvin -

PS: Yes, the last line is a joke.

- Raw text -


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