| Re: [AD] new_api_branch news |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] new_api_branch news
- From: Elias Pschernig <allefant@xxxxxxxxxx>
- Date: Tue, 26 Oct 2004 03:19:16 +0200
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=N+ngDvkzyXc5ydPwybjM4D1xFTLK8PflW/jrqlBiCoSlkNDxc3rE6xffRd2uDsoNqYcoj3sDu6Wc9Wgb83rjDxNFo4uMGlHkEsAnwiutfrZwyncB98ZKmB1Cgaj11dg05ZGlCzRgWnUTidvwjnLccKj5Cdr97JcXHL+o8f5XTho=
Hm - you're right, there's not much in the todo.txt for unix/X11.
Since you're a perl wizard - you could prototype a ._tx -> XML
converter in perl, I'm more and more thinking we should follow that
idea.. the DTD for such an XML format can be found here:
http://alleg.sourceforge.net/future/allegro_xml_documentation_dtd_draft_5.zip.
But it would be rather boring, so I don't really want to suggest this.
Let me see, what is needed for Allegro itself.. X11 graphics work,
even DGA works with minor glitches. mouse works, Evert has his patch
to use the X11 cursor, i made a patch for X11 keyboard (no idea why it
doesn't appear on the list, i sent it hours ago). Speeding up X11 is
something which needs more investigation.. bah, it's too late right
now, I can't think of anything for X11..
Testing the ALSA driver certainly is a good idea, I'm still puzzled
what exactly that incompatibility between our systems was.. I'm mostly
blaming ALSA though.
Hm, and there was some demand for memory packfiles on allegro.cc...
Anyway, just try to find something which is broken or could work
better - I always seem to find a few things just by running any
Allegro program :)