I added a section titled &quot;extending ChucK&quot; at the end of the manual and moved the chapter on LicK there. This is meant to avoid obscuring the line between what is and isn&#39;t a part of ChucK for new users, who will quite likely already be feeling a bit overwhelmed. Similar initiatives like SMIRK and SMULE could find a introduction there too, as could Steve&#39;s notes on building UGens using Faust and potential future notes on dealing with the source itself, in case somebody would feel up for that.<br>
<br>I&#39;m close to calling it a night. Some notes; this is a great initiative, it clearly works and it&#39;s a lot of fun. This is much, much preferable to Adam going at it alone, chiefly because Adam&#39;s time, like everyone&#39;s, is limited. It still needs a lot of work though. There are still big gaps and I noted some spots where the explanation may be 100% correct but would also be utterly incomprehensible to anyone without a background in math. I&#39;d like to suggest that this text should be readable to a teenager with a passion for sound/music and a interest in computers who may not have a formal background in either. I think this might lead to starting a description with a informal introduction and perhaps a analogy that may be followed by &quot;programmers would call this [formal description goes here]&quot;. I&#39;m not talking about &quot;dumbing things down&quot; here, more about a clear explanation of why we are introducing a subject to make it evident why it will be worthwhile to read about it. Once it&#39;s clear what things are good for and how they are unlike other things it will hopefully also be clear that it&#39;ll be useful to learn a specialised vocabulary to talk about them.<br>
<br>Yours,<br>Kas.<br>