Re: [AD] Proposed changes for Allegro 5 (6?)

[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]



On Tue, 27 Nov 2001, Bob wrote:

> http://pages.infinit.net/voidstar/newalleg.txt

Splitting packfiles handling to compression/encryption layers is good, but
removing default implementation is bad, bad, bad :-) Why?

Adding networking is not good thing, I think. Too much new code without
any connection to current Allegro.

Allegro 5 should have cleaner and consistent API with better decomposition
to modules (unicode handling, gfx, sound, input, packfiles, etc.). This
should be the main goal. And, of course, cleaning up the sources a bit.

Generated API docs is very good idea, but forget Javadoc. It's too
Java-centric and too slow.

Have a nice day.

Stepan Roh



Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/