<!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 11:36 AM, Jonathan Wilkes wrote:
<blockquote cite="mid:901477.36009.qm@web51504.mail.re2.yahoo.com"
type="cite">
<style type="text/css"><!-- DIV {margin:0px;} --></style>
<div
style="font-family: times new roman,new york,times,serif; font-size: 12pt;">How
exactly
would one "start to work" on the Pd Manual?<br>
<br>
More specifically:<br>
What is the process by which a new, professionally written manual
replaces the old, error-ridden manual?<br>
</div>
</blockquote>
<br>
"Replaces" is perhaps not quite the right word. Last year I wrote and
released "The Inform 7 Handbook" (nothing to do with music -- you can
find it on my website at <a class="moz-txt-link-abbreviated"
href="http://www.musicwords.net/if/i7hb.htm">www.musicwords.net/if/i7hb.htm</a>,
if you're
curious), because I felt the existing documentation for Inform 7 was
inadequate. My work didn't replace the manual. It simply offered a
coherent, all-in-one-place introduction to the basics. I've gotten very
good feedback on it from users.<br>
<br>
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.<br>
<br>
If someone wants to write this, you could probably talk me into giving
it an edit. As a relative newbie to Pd, I would be a good test case,
and as an experienced tech writer I would be able to make suggestions.<br>
<br>
--JA
</body>
</html>