<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I'm almost finished revising the docs: 2.control.examples,<br>
3.audio.examples, 4.data.structures, and 5.reference. I'll post them to<br>
the list when I'm done (should be shortly).<br>
<div class="im"><br></div></blockquote><div><br>cool!<br><br><br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
>Anyway learning Pd is _not_ easy and it doesn't have to be. Hence the >learning curve and learning tools could be improved, but you still should >be aware that if you want to be able to master such a flexible computing >capability you need to get your hands (and mind) dirty. I think it's >worth, and I wouldn't like it to be easier.<br>
<br>
</div>I disagree-- I would like it to be easier, and it should be easier. More<br>
time spent trying to figure out how dollarsym atoms get expanded is less<br>
time spent making music. The last paragraph of Pd Manual 2.6.5 doesn't<br>
reflect the current state of Pd, btw. Do items like that belong on the<br>
bug tracker?<br>
<div class="im"><br></div></blockquote><div><br><br>Well, I agree It could be a better learning, but Michael stole my thought:<br><br>" If I am not interested in solving problems<br>
algorithmically through programming, I will not use Pd but some other<br>
software that will help me accomplish my goals via some other means<br>
that I can understand better."<br>
<br><br><br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
>Studying and Teaching I found Pd can operate kind of "natural selection" >that sometimes is needed in some context.<br>
<br>
</div>By that logic there should be even less documentation (or more outdated/<br>
erroneous docs). But what are the characteristics that make students fit<br>
enough to avoid death and reproduce themselves into the next generation of<br>
the Pd learning environment? As far as I can tell, Pd crashes will remain<br>
Pd crashes, regardless of whether the output isn't boring, so I don't<br>
think I understand what you mean.<br></blockquote><div><br>mm.. why less documentation? Could be better and updated documentation as you are doing. Be sure that who's studying and teaching to learn Pd (and not to _instantly_ make music) will be very grateful (i am the first!)<br>
ehehe, probably my statement was slightly "racist", apologies, I only mean "what makes students fit enough to use Pd, or to die in the boredom of User-friendly soft".<br>The _process_ of learning any kind of programming language play an essential role in the way you will use it in the future.<br>
As Michael outlined too, I don't think it would be useful to show students there exist a supercool ready-made drum sequencer, but i prefer to teach first how to load a sample in a table, explaining how they can get a drum sequencer from there.<br>
Talking about Pd It's fundamental to learn how things works, imho.<br></div><div><br><br> </div></div><br>-- <br>Marco Donnarumma aka TheSAD<br>Independent New Media Arts Professional, Performer, Teacher - Edinburgh, UK<br>
<br><br>PORTFOLIO: <a href="http://marcodonnarumma.com">http://marcodonnarumma.com</a><br>LAB: <a href="http://www.thesaddj.com">http://www.thesaddj.com</a> | <a href="http://cntrl.sourceforge.net">http://cntrl.sourceforge.net</a> | <a href="http://www.flxer.net">http://www.flxer.net</a><br>
EVENT: <a href="http://www.liveperformersmeeting.net">http://www.liveperformersmeeting.net</a><br>