RE: [Alleg5] Behold the Next Generation of Allegro: AllegroPro

[Korval <Ko...@co...>]

Well, there is a roadmap. It's accepted by me ;) I'm committed to seeing
this project through, at the very least, to the point where other people can
work on it, and I intend on following that roadmap.

In any case, from your postings in the Allegro 4 ML, you seem to be pretty
knowledgeable about hardware sound. I don't have any real understanding of
sound, hardware or otherwise. Certainly not enough to be able to go and
design a good, hardware-compatible, sound API.

So, I'm asking you to lend this project your expertise and design a sound
system. What I'm looking for out of a design is not a bare list of feature.
Look at what I did for graphics; I went so far as to specify, line by line,
precisely how blitting works. I want a similarly in-depth document detailing
regarding sound features. API functions are not to be defined; it is enough
to say that there is such an API. Naming the functions and parameters is not
reasonable for a design document. That kind of thing comes later.

If you accept my invitation, don't feel constrained to stay within the
limits of Allegro 4's sound API. The determining factors in your design
should be:

1: What makes for good, fast hardware implementation?
2: What makes things relatively nice for the user?

Note that your emphesis should be on hardware-based sound, not software.
AllegroPro is trying to encourage high-performance game programming, not
high-compatibility with age-old architectures.

-----Original Message-----
From: all...@li...
[mailto:all...@li...]On Behalf Of Karthik
Kumar V
Sent: Sunday, April 18, 2004 8:55 AM
To: all...@li...
Subject: Re: [Alleg5] Behold the Next Generation of Allegro: AllegroPro


Hi,

Nice design. I have always fancied about Allegro5 being the best, easy to
use API ever for makimg games.

When we see Allegro5, it shouldn't just include the core libraries alone,
it should be something that anybody can get used to and work.
Like, if you take the value proposition to an end-user of Allegro, he
should see its advantages as a potential game development toolkit than
something on the lines of DirectX and OpenGL. :P Well, I'm sure not all
people would agree with this, but what I'm saying is: think about it.

We people should pool in our ideas to make it a extensive, generic,
bug-free,
easy to use API. The reason why I think Allegro stands out as an excellent
game programming tool, is because of its ease of use in spite of powerful
features. So, that's all I'm saying....

Is there a formalized roadmap, accepted by everybody for development?
Please do let us all know.