From: Adam Seychell Subject: a newbie overwhelmed with this API Date: Sat, 04 Aug 2007 21:50:24 +1000 Message-ID: <46B46800.6020509@yahoo.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail06.syd.optusnet.com.au (mail06.syd.optusnet.com.au [211.29.132.187]) by alsa0.perex.cz (Postfix) with ESMTP id 25FBC1038A5 for ; Sat, 4 Aug 2007 13:50:28 +0200 (CEST) Received: from [192.168.0.106] (c211-28-147-59.brodm2.vic.optusnet.com.au [211.28.147.59]) (authenticated sender eseychell) by mail06.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id l74BoPxK001638 for ; Sat, 4 Aug 2007 21:50:25 +1000 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org I'm writing simple audio application and I have successfully used the DirectSound API under Windows. Now I'm looking at porting to Linux using ALSA. I have tried reading the online ALSA API documentation, but it seems too early in development and insufficient compared what one can learn reading Microsoft's DirectX SDK documentation. Excuse my ignorance for a minute, but the API seems quite large compared to DirectSound and so I'm wondering if there is good reason why so many functions exists ? Was there an early design decision not to write ALSA in C++ ? I would like to help out with documentation but of course I thats impossible for someone who is a complete novice to the ALSA project. I know that writing good documentation takes a lot of hard work, especially for software developers who spend enough time on coding. Its an unfortunate paradox among all open source projects. Software developers who posses the knowledge can't readily communicate it to potential volunteer documentation writers in an open source environment. Adam