Re: [linux-audio-dev] How non-programmers use documentation.
On Tuesday 28 August 2001 10:45 am, you wrote: > Alexander Ehlert wrote: > > > >16. Non-programmers that I talked to have never sent a bug report or a > > > >feature request to a software company. The idea of sending one > > > > directly to a programmer or a technical writer was a completely > > > > foreign concept. > > > > I consider this a bad attitude in open source land. > > certainly. > maybe there should be an extra section in each readme to inform > newbies how essential bug reports are, and that they are required > "payment" for the use of free software. > this is something the distro vendors should take into account more. > > i use suse, and it's dead easy to install, so yes, you can go from > windows to linux in a day. they have three or four printed books in > their package, but it still lacks an extensive chapter on > open-source culture (they do print the gpl, but who would want to > read that ?). Tell them to read "The Cathedral and the Bazaar". : ) Good book for understanding open-source. Greg > are the other distributors doing any better in this respect ? > > jörn
RE: [linux-audio-dev] How non-programmers use documentation.
> -Original Message- > From: Paul Sladen [mailto:[EMAIL PROTECTED]] > > On Tue, 28 Aug 2001, dany wrote: > > > I believe the new filetree-standard under linux will help a > lot: if I know my > > distro is compliant, if I know the prog I try to install is > compliant, then I > > can say there's a bug or not. Elsewhere I'm in doubt. > > The other alternative is to standardise on Debian, and then > just wait until > the rest of the world catches up. that's basically the current situation:-) erik
Re: [linux-audio-dev] plugins
Hello! On Tue, 28 Aug 2001, Frank Neumann wrote: > Are you sure you only installed the LADSPA plugins in one directory? > That is, if (as recommended) your LADSPA_PATH is set to > /usr/local/lib/ladspa, what files are under that directory? I had all the LADSPA paths listed twice. josef:~$ echo $LADSPA_PATH :/home/mike/.ladspa:/usr/local/lib/ladspa:/usr/lib/ladspa:/home/mike/.ladspa: /usr/local/lib/ladspa:/usr/lib/ladspa That was the problem. Just as Richard said, thanks. Miha... - Miha Tomšič --- C. na postajo 55 -- SI-1351 Brezovica pri Lj. --- SLOVENIA -
Re: [linux-audio-dev] How non-programmers use documentation.
Alexander Ehlert wrote: > > >16. Non-programmers that I talked to have never sent a bug report or a > > >feature request to a software company. The idea of sending one directly to > > >a programmer or a technical writer was a completely foreign concept. > > I consider this a bad attitude in open source land. > certainly. maybe there should be an extra section in each readme to inform newbies how essential bug reports are, and that they are required "payment" for the use of free software. this is something the distro vendors should take into account more. i use suse, and it's dead easy to install, so yes, you can go from windows to linux in a day. they have three or four printed books in their package, but it still lacks an extensive chapter on open-source culture (they do print the gpl, but who would want to read that ?). are the other distributors doing any better in this respect ? jörn -- Jörn Nettingsmeier home://Kurfürstenstr.49.45138.Essen.Germany phone://+49.201.491621 http://icem-www.folkwang-hochschule.de/~nettings/ http://www.linuxdj.com/audio/lad/
[linux-audio-dev] Articles about writing documentation.
Following up on my previous thread, here are some articles about writing documentation that I found interesting... _How to Publish a Great User Manual_ by Bruce Tognazzini on AskTog.com http://www.asktog.com/columns/017ManualWriting.html _Manuals: Simplicity a Virtue?_ by Bruce Tognazzini on AskTog.com http://www.asktog.com/readerMail/2000-04ReaderMail.html _Manuals: They Can Be Good_ by Arnold Hendrick on Gamasutra.com http://www.gamasutra.com/features/1999/Hendrick_01.htm _Task-Centered User Interface Design: A Practical Introduction_ by Clayton Lewis and John Rieman Chapter 7 covers the topic of manuals. Please note that it is share-ware. http://hcibib.org/tcuid/chap-7.html === Kevin Conder, [EMAIL PROTECTED]
Re: [linux-audio-dev] How non-programmers use documentation.
Very good point. I could not put my finger on it, but you are right, what often stops you from sending bug reports is that you don't want to be taken for a fool :-). BR /Robert dany wrote: Le Lundi 27 Août 2001 20:59, vous avez écrit : >16. Non-programmers that I talked to have never sent a bug report or a >feature request to a software company. The idea of sending one directlyto >a programmer or a technical writer was a completely foreign concept. errh errh in my case (I can't use effects in grecord, it core-dumps) I don't want people to say "hey your machine is a mess" "oh oh you don't know how to install this ot that!". I'm kidding a little, but not too much.I believe the new filetree-standard under linux will help a lot: if I know my distro is compliant, if I know the prog I try to install is compliant, then I can say there's a bug or not. Elsewhere I'm in doubt. Shall I say I'm a bit scared applying the low-latency patches? I've tried but got some errors during compilation. So I gave up.
Re: [linux-audio-dev] How non-programmers use documentation.
On Tue, 28 Aug 2001, dany wrote: > I believe the new filetree-standard under linux will help a lot: if I know my > distro is compliant, if I know the prog I try to install is compliant, then I > can say there's a bug or not. Elsewhere I'm in doubt. The other alternative is to standardise on Debian, and then just wait until the rest of the world catches up. Paul
Re: [linux-audio-dev] How non-programmers use documentation.
Le Lundi 27 Août 2001 20:59, vous avez écrit : > > >16. Non-programmers that I talked to have never sent a bug report or a > > >feature request to a software company. The idea of sending one directly > > to >a programmer or a technical writer was a completely foreign concept. errh errh in my case (I can't use effects in grecord, it core-dumps) I don't want people to say "hey your machine is a mess" "oh oh you don't know how to install this ot that!". I'm kidding a little, but not too much. I believe the new filetree-standard under linux will help a lot: if I know my distro is compliant, if I know the prog I try to install is compliant, then I can say there's a bug or not. Elsewhere I'm in doubt. Shall I say I'm a bit scared applying the low-latency patches? I've tried but got some errors during compilation. So I gave up.
Re: [linux-audio-dev] Women Only !!
Le Samedi 18 Août 2001 21:24, the masked spammer wrote: > has marched into the lives of men--seven million men used Viagra last year > alone. Now women are getting the chance to receive a similar gift--a light, > pleasant creme designed for females only. Well men, there 's not only music and computas in life! :D
Re: [linux-audio-dev] plugins
Hi, [EMAIL PROTECTED] wrote: > I finally installed LADSPA. Great thing! > > Well there is a little "but". Every listplugins lists every plugin twice. > The same happens when TerminatorX loads the plugins. > > What's the deal? Are you sure you only installed the LADSPA plugins in one directory? That is, if (as recommended) your LADSPA_PATH is set to /usr/local/lib/ladspa, what files are under that directory? Are you sure ALL plugins are listed twice? Maybe it's only the plugins in the cmt.so archive, and you have two copies of this archive in your LADSPA search path? You could try doing something like "strace -e open listplugins" to see what files are actually accessed for the listing. I have no such problems.. Greetings, Frank -- Frank Neumann ([EMAIL PROTECTED]), VIONA Development Center ST Microelectronics, Karlstraße 27, 76133 Karlsruhe
