<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 6/7/2010 2:00 PM, Dan Wilcox wrote:
<blockquote cite="mid:B92EE080-BA93-4DB7-82C7-B572CB0F9BB2@gmail.com"
type="cite"><br>
<div>
<div>On Jun 7, 2010, at 9:04 PM, Jim Aikin wrote:</div>
<br>
<blockquote type="cite">
<div bgcolor="#ffffff" text="#000000">I think that would probably
be the way to go with Pd documentation as
well -- some sort of handbook that gives users step-by-step
instructions on all of the basic things they will need or want to do
when getting started. Once they're up and running, they will be able to
find more advanced information wherever it's tucked away.<font
class="Apple-style-span" color="#000000"><font class="Apple-style-span"
color="#144fae"><br>
</font></font></div>
</blockquote>
<br>
</div>
<div>You mean like Johannes Kreidler's <a moz-do-not-send="true"
href="http://www.pd-tutorial.com/">Programming Electronic Music in Pd</a>?</div>
</blockquote>
<br>
Could be. I'll have a look at it -- thanks for the link. In general,
however, I would suggest that a website-based multi-page manual is
always a bad idea, for two reasons: First, because it's not searchable.
Second, because it's an invitation to the author to jumble things up
and leave some pages blank "to be filled in later." This is not a
criticism of Kreidler's work, which I haven't read, it's just a general
observation based on other things I've seen.<br>
<br>
What one wants, I think, is a single PDF file that, in the absence of
an index, can be searched for text strings, and that is conceived and
written in a linear, coherent manner.<br>
<br>
--JA<br>
<br>
</body>
</html>