<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">I probably won't have enough time to work out all the kinks, so waiting until the next version is fine.<br><br>-Jonathan<br><br><div style="font-family: arial,helvetica,sans-serif; font-size: 10pt;"><font face="Tahoma" size="2"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Hans-Christoph Steiner <hans@at.or.at><br><b><span style="font-weight: bold;">To:</span></b> Jonathan Wilkes <jancsika@yahoo.com><br><b><span style="font-weight: bold;">Cc:</span></b> pd-dev@iem.at<br><b><span style="font-weight: bold;">Sent:</span></b> Mon, June 7, 2010 8:10:40 PM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [PD-dev] Updating pd help patches<br></font><br>
<br>I think you've been doing a lot of working this, and its a great thing.<br> So getting SVN access means that you don't have to wait on anyone, you<br>can just commit directly. SVN isn't so difficult to learn, so its worth it.<br><br>As for integrating this patches into Pd-extended, I'd prefer we aim for<br>the next version, unless you have time to make sure all of the bugs,<br>etc. are fixed. That means testing them a lot in the release cycle<br>since they won't have been in the auto-builds for all these past months.<br><br>.hc<br><br>Jonathan Wilkes wrote:<br>> Hi,<br>> I sent an email to the user list, but I guess it belongs here instead. I have revised almost all of the help <br>> patches for vanilla objects to conform to the PDDP template created a few years back. Each patch lists <br>> info for xlets, args, and related objects and has a [pd META] subpatch with info that can be used if
<br>> someone makes a plug-in to search for objects (I made a simple patch called search-test.pd as a demo).<br>> <br>> All patches are the same size and are located at origin 0,0 (top left of screen) so that at least part of the <br>> patch will be visible at any screen resolution. Each patch also has a pddplink at the bottom left to a general <br>> "Help" patch (pddp/help.pd) that links to:<br>> * a help page for the pd help system<br>> * the Pd Manual<br>> * various tutorials (control, audio, intro to gem, dynamic patching, etc.)<br>> * other resources like the all_about_* patches (which I've revised and added to)<br>> <br>> There is also a decent attempt at cross-referencing, so that, for example, the help patch for delread~ <br>> has a pddplink to the audio tutorials where that object is used (G01, G02, G05). Each help patch also has <br>> a link to the respective pdpedia web page (although I'm not
sure that this will turn out to be all that useful).<br>> <br>> I'm also in the middle of adding [pd META] tags to all the externals included in pd-ext, as well as creating <br>> help patches for the objects that don't currently have one.<br>> <br><span>> The patches are all at: <a target="_blank" href="http://puredata.info/Members/jwilkes/doc/at_download/file">http://puredata.info/Members/jwilkes/doc/at_download/file</a></span><br>> <br>> As I said in my email on the user list, I've never used SVN before, but I'm happy to learn it if that's the <br>> easiest way to get them into pd-ext. As for the revisions of external help patches, I'm not sure what the <br>> best way is to implement my changes, since those help patches belong to their respective developers.<br>> <br>> I would appreciate suggestions anyone has on the best way to proceed.<br>> <br>> Thanks,<br>> Jonathan<br>> <br>> <br>>
<br>> <br>> <br>> <br>> ------------------------------------------------------------------------<br>> <br>> _______________________________________________<br>> Pd-dev mailing list<br>> <a ymailto="mailto:Pd-dev@iem.at" href="mailto:Pd-dev@iem.at">Pd-dev@iem.at</a><br><span>> <a target="_blank" href="http://lists.puredata.info/listinfo/pd-dev">http://lists.puredata.info/listinfo/pd-dev</a></span><br><br></div></div>
</div><br>
</body></html>