Re: [AD] Screen update API again |
[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]
Evert Glebbeek wrote:
On Wednesday 25 August 2004 15:24, Angelo Mottola wrote:Basically my question is: are we going to emulate the new API using the old API calls, or are we going to emulate the old API using new API calls?My take, in this case on the graphics API, is to get a working version as soon as possible so that it can be tested. This means setting it on top of current functions. Then, when consensus is reached about the API, the situation is inverted and the old API is reworked into a compatibility layer.
I suppose it would go something like this: first set up the framework of the new gfx API on top of the current implementation. When the subset of functionality corresponding to the old API also works under the new API, do the inversion, then continue extending/generalising the implemention so the new API gets the rest of the functionality it's supposed to have.
I think Peter followed the opposite approach with his timer/thread API.
Yeah. I'd already written the code from scratch (actually, I reused a ton of code), and the new event queues API would've been impossible to layer on top of what Allegro has currently.
Peter
Mail converted by MHonArc 2.6.19+ | http://listengine.tuxfamily.org/ |