On Mon, 04 Sep 2006 16:31:10 +0200 Takashi Iwai <[EMAIL PROTECTED]> wrote:
> At Mon, 04 Sep 2006 07:15:54 -0400, > Gene Heskett wrote: > > > > On Monday 04 September 2006 06:46, Takashi Iwai wrote: > > >At Mon, 4 Sep 2006 13:32:27 +0300, > > > > > >Sergei Steshenko wrote: > > >> On Mon, 4 Sep 2006 18:25:10 +0800 > > >> > > >> "littertiger" <[EMAIL PROTECTED]> wrote: > > >> > hi, group > > >> > How to develop and configure plugins? I find the document is too > > >> > brief. anyone cound suggest some materials,or book? > > >> > > > >> > Best Regards > > >> > littertiger > > >> > [EMAIL PROTECTED] > > >> > 2006-09-04 > > >> > > >> As I understand the situation, ALSA developers are fiercely opposed to > > >> writing end user documentation unless they are payed for this :-) . > > > > > >Well, more correctly, unless they give us time and guts for this. > > >(and irony won't give neither of them :-) > > > > > I'm not sure if that was irony, Takashi. Besides, the word is "paid". > > That what I mentioned. Also, another correction: developers are not > "opposing" but less interested (in comparison with the demand from > end-users :-) > > > But, it seems to me that at some point the developers are going to be so > > buried in this that the only way to save your sanity is to write some docs > > that at least specify how its done for the rapidly proliferating chip > > selections that the chip people have succeeded in actually making a racket > > with that passes for sound in most circles. Without this, each developer > > will keep re-inventing the wheel. That doesn't appear to be the best way > > to spend your often valuable time. > > Well, in your argument it's not clear what level of documentation is > urgently needed. Actually, the difficulty in writing a document for > end-users is to know what they don't/need to know -- or a definition > of "end-users". We may need a tecnical reference for the developers, > while we may need a guidebook for novice users, or Gospels for > ex-window users. My mother cannot use a video recorder unless someone > tells her how to use it. But it's bundled with a good technical > reference for all information. > > Maybe we should start from FAQ, then someone can compile it as a > real tutorial (if needed)... > > > Takashi > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Alsa-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/alsa-user > At least, answer this question already in documentation: http://alsa.opensrc.org/.asoundrc -> " What is a slave in the first place? What does it do, what does it mean, what for do I need it? Can please add some more light on this?' ". Second, as I already said, write down and publish states of card controls as you are testing the cards while debugging the drivers, so we, end users, will know how to set controls in order to enable certain card features. --Sergei. -- Visit my http://appsfromscratch.berlios.de/ open source project. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Alsa-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/alsa-user
