--20cf30051230cd406804b2c28377
Content-Type: text/plain; charset=ISO-8859-1
I also think it's a much needed idea. I'd be happy to do some contributing
too, but like Harry, will need my contributions looked over by experts!
iain
On Sun, Nov 27, 2011 at 4:44 PM, Andrew C wrote:
> Hiya Harry,
quoted text >
> On Mon, Nov 28, 2011 at 12:31 AM, Harry van Haaren
> wrote:
> > I think some "beginner" coding documentation on Linux Audio would be a
> great
> > asset to the community, and I'm willing to contribute to such an effort.
> As
> > Robin Gareus mentioned in another thread, a "FLOSS" manual is probably
> the
> > best way to go for a community effort on documenting.
>
> I rather like this idea, for what it's worth.
>
> > "if
> > you think it should be thought that way write the tutorial"... the
> downside
> > of this is that if one tutorial uses toolkit and the next toolkit
> ,
> > the average beginning coder is going to get lost in implementation
> details
> > and that defeats the purpose of documentation :D
>
> Easier said than done, but why not use the most popular toolkits for
> each tutorial, that way you can follow each tutorial using whichever
> toolkit you want.
>
> Andrew.
>
> (hurray for me ignoring the amount of work the above statement would
> involve, but it's an idea.)
> _______________________________________________
> Linux-audio-dev mailing list
>
Linux-audio-dev@lists.linuxaudio.org
>
http://lists.linuxaudio.org/listinfo/linux-audio-dev
>
--20cf30051230cd406804b2c28377
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
I also think it's a much needed idea. I'd be happy to do some =
contributing too, but like Harry, will need my contributions looked over by=
experts!iain
On Sun, Nov 27, 2011 at 4:44 PM, Andrew C <countfuzzball@gmail.com > wrot=
e:
Hiya Harry,
On Mon, Nov 28, 2011 at 12:31 AM, Harry van Haaren
<harryhaaren@gmail.com > =
wrote:
quoted text > I think some "beginner" coding documentation on Linux Audio =
would be a great
quoted text > asset to the community, and I'm willing to contribute to such an e=
ffort. As
quoted text > Robin Gareus mentioned in another thread, a "FLOSS" manual i=
s probably the
quoted text > best way to go for a community effort on documenting.
I rather like this idea, for what it's worth.
> "if
quoted text > you think it should be thought that way write the tutorial"...=A0=
the downside
quoted text > of this is that if one tutorial uses toolkit <X> and the next to=
olkit <Y>,
quoted text > the average beginning coder is going to get lost in implementation det=
ails
quoted text > and that defeats the purpose of documentation :D
Easier said than done, but why not use the most popular toolkits for<=
br>
each tutorial, that way you can follow each tutorial using whichever
toolkit you want.
Andrew.
(hurray for me ignoring the amount of work the above statement would
involve, but it's an idea.)
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@lis=
ts.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
--20cf30051230cd406804b2c28377--