[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: [AD] Sound API attempt
- From: Chris <chris.kcat@xxxxxxxxxx>
- Date: Sun, 15 May 2005 22:39:27 -0700
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:content-type:content-transfer-encoding; b=Zt/dXa7bASc/ovWGavEihdjBOg3HYuJsY0Oooc4PJNPns0YIdu2g5Lia0WUJJDgbmvvL5Zew+vtDmpCAxV4tI9Ed+3iAEBIlvYx4TKXult5winz3RUmtXL/LkEYj0r9xxnC5DP7X4AuC6+oe3gnSIsbC+RLo8S/4oUY0++RYfy0=
Okay, I decided to give rewriting the sound API another attempt. I think
it's coming along well, although before I get too far I wanted to show
it around to make sure I'm not doing something stupid, or improper, or
something that'll harm expandibility later on.
A very basic beginning can be found here:
http://kcat.strangesoft.net/sound.c
It is in no way, shape, or form suitable to be put into the new api
branch, but I hope it's good enough to show that there is /soemthing/
being worked on. Questions, comments, and concerns welcome.