From: Josh Green <jgreen@users.sourceforge.net>
To: cliff@postmaster.co.uk
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: documentation - yeah right!
Date: 20 May 2003 13:31:08 -0700 [thread overview]
Message-ID: <1053462667.2171.27.camel@SillyPuddy> (raw)
In-Reply-To: <PM.9386.1053461408@pmweb11.uk1.bibliotech.net>
On Tue, 2003-05-20 at 13:10, Cliff Bradshaw wrote:
> If alsa is supposed to be so profesional, why does it have no decent documentation?
>
> I have searched the whole internet and still cant find any proper documentation on how to use the fscking sequencer interface!
>
> sure there is the howto by Matthias Nagorni, (thank god *someone* is writing docs for the seuqncer!) but I want to see a proper API reference
>
> doxygen is just an excuse to avoid writing documentation and should be banned from all projects. If I want a list of all the damn globals I'll look in the source code thankyou.
>
> seriously though. Alsa is great, but is not going to suceed unless we know how to use it. OSS has pretty good documentation and it will continue to be the standard linux audio api unless we tell people how to use alsa!!!!!!!!!
>
Perhaps you are being confused with how to navigate the doxygen
reference (a rather easy thing to do). If this is the case, try going to
the "File List" link at the top of the ALSA library reference and then
click on seq.c in the list and you will see all the routines used for
the sequencer. Clicking on one will give you more details. The only
thing I find a little annoying by the reference docs is that the pages
are so huge (perhaps because most routines are documented :).
Another good source of reference would be to take a look at some example
programs (there are some in the "test" directory in the alsa-lib
source).
Your request for help is less likely to succeed with the tone in which
you are writing, though. Keep in mind that many of the individuals
working on this are doing so in their spare time, because they like
doing it. Its people that bad mouth this that are more likely to cause
it to not succeed than anything else, free software developers like to
be appreciated for their work. Cheers.
Josh Green
-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
next prev parent reply other threads:[~2003-05-20 20:31 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 20:10 documentation - yeah right! Cliff Bradshaw
2003-05-20 20:16 ` Jaroslav Kysela
2003-05-20 20:31 ` Josh Green [this message]
2003-05-20 20:52 ` Kai Vehmanen
2003-05-20 22:11 ` David Stuart
2003-05-20 22:08 ` Paul Davis
2003-05-20 23:53 ` Drake Wilson
2003-05-21 5:02 ` Patrick Shirkey
2003-05-21 7:34 ` Giuliano Pochini
2003-05-21 14:43 ` Richard Cochran
2003-05-21 15:24 ` Paul Davis
2003-05-21 15:50 ` Paul Davis
[not found] ` <200305211518.h4LFI2jE027163@mail.cs.umass.edu>
2003-05-21 15:59 ` Richard Cochran
2003-05-21 16:52 ` Kai Vehmanen
2003-05-21 17:16 ` Richard Cochran
2003-05-21 17:36 ` Kai Vehmanen
2003-05-21 17:39 ` Jaroslav Kysela
2003-05-21 17:49 ` Paul Davis
2003-05-21 17:03 ` Paul Davis
[not found] ` <200305211657.h4LGvKjE024721@mail.cs.umass.edu>
2003-05-21 18:08 ` Richard Cochran
2003-05-22 1:28 ` Patrick Shirkey
2003-05-21 16:09 ` Richard Cochran
2003-05-21 16:44 ` Paul Davis
2003-05-22 13:16 ` PCI write barrier Giuliano Pochini
2003-05-23 10:30 ` Takashi Iwai
2003-05-22 12:47 ` documentation - yeah right! Takashi Iwai
2003-05-22 13:39 ` Jaroslav Kysela
2003-05-22 14:51 ` Pieter Palmers
2003-05-22 14:18 ` Richard Cochran
2003-05-22 15:33 ` Takashi Iwai
2003-05-22 16:57 ` Jack O'Quin
2003-05-22 17:03 ` Patrick Shirkey
2003-05-22 17:08 ` Richard Cochran
2003-07-11 0:23 ` i810 - no sound from cvs snapshot Richard Cochran
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1053462667.2171.27.camel@SillyPuddy \
--to=jgreen@users.sourceforge.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=cliff@postmaster.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.