<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Oh yes, love it. This may actually do all I need.<div><br></div><div>In particular, I like how "killall chuck" restarting the libraries will make it so much quicker to try out public classes. I mean, even though it's kind of slow, at least with a scripting language like Python it'll run on other computers.</div><div><br></div><div>One improvement I can think of is to figure out what chuck kicks back when it's fully loaded, and use that rather than time.sleep(1). It could just run into some problems depending one any kind of lags in the load time. And, considering this is totally based on crashing chuck, it should assume that not everything will work properly.</div><div><br></div><div>Maybe kick back a warning if chuck doesn't start after 5 seconds or so. I don't know, just more ideas. And finally, maybe just have setupfile set to an optional argument. That would allow multiple chuck handles to run at once using different libraries (if, for example, you want different chucks on different osc ports).</div><div><br></div><div>For the record, I've also got a Mac with Snow Leopard, so we've deduced nothing so far about compatibility. Great work, though--let me know if I can help.</div><div><div><br></div><div>-Andrew</div><div><br><div><div>On Jun 15, 2010, at 5:58 PM, mike clemow wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Okay folks,<div><br></div><div>It's hacky and slow, but it does technically work (on my Mac with Snow Leopard...) </div><div><br></div><div>how to: </div><div><br></div><div>1) make sure chuck is installed ;)</div><div>
2) unzip the archive, open a terminal window</div><div>3) cd /path/to/chuck-session-handler_v01</div><div>4) python csh-v1r0.py - notice that the script starts chuck and adds the <a href="http://setup.ck/">setup.ck</a> and <a href="http://mylib.ck/">mylib.ck</a> files</div>
<div>5) open another terminal window</div><div>6) in that terminal window cd /path/to/chuck-session-handler_v01</div><div>7) chuck + <a href="http://test.ck/">test.ck</a></div><div>8) verify that the output (in the first window) prints "5 :(int)"</div>
<div>9) killall chuck</div><div>10) notice that the script reboots chuck and adds the <a href="http://setup.ck/">setup.ck</a> and <a href="http://mylib.ck/">mylib.ck</a> files</div><div>11) chuck + <a href="http://test.ck/">test.ck</a></div>
<div>12) verify that the output (in the first window) prints "5 :(int)"</div><div>13) rinse, repeat...</div><div><br></div><div>Questions, comments, concerns? I think that something like this could be very interesting as part of an incremental programming system that would keep track of the classes that were written and add them to the list of classes that are included in <a href="http://setup.ck/">setup.ck</a>. I think that this would be interesting for building and maintaining libraries for live-coding.</div>
<div><br></div><div>Anyway, it's a start... of something.</div><div><br></div><div>Best,</div><div>Mike</div><div><br></div><div><br><br><div class="gmail_quote">On Tue, Jun 15, 2010 at 2:57 PM, mike clemow <span dir="ltr"><<a href="mailto:michaelclemow@gmail.com">michaelclemow@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">> By the way: good programmers enforce legible code, not languages. :)<br><br></div><div>Yes, Joe, but if *I* write it in Perl, it will be crap code. :)</div>
<div><br></div><div>I'm working on a Python stub application for this session handler idea. We can use it as a basis and build on it, if you guys like it. What Andrew and I were talking about doing is actually quite different than what Scott Wheeler's original Perl script did. I'm much more interested in the session handler idea, but I'm sure there's a way to combine them. I personally don't think it makes much difference what language they two are written in as long as they play nice together.</div>
<div><br></div><font color="#888888"><div>Mike</div></font><div><div><div></div><div class="h5"><br><div class="gmail_quote">On Sat, Jun 12, 2010 at 10:29 PM, Joe McMahon <span dir="ltr"><<a href="mailto:mcmahon@ibiblio.org" target="_blank">mcmahon@ibiblio.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2010/6/12 mike clemow <<a href="mailto:michaelclemow@gmail.com" target="_blank">michaelclemow@gmail.com</a>>:<br>
<div>> I would be happy to help make something too, although I would say we should<br>
> use Python for two reasons:<br>
> 1) I know Python much better than Perl.<br>
> 2) Python enforces much more legible code.<br>
</div>Okay, well, I'll take a look at the Perl version; let's see what we<br>
can come up with.<br>
<br>
By the way: good programmers enforce legible code, not languages. :)<br>
Programming languages can help out, but it's possible to write crap<br>
code in any language. Having written both, I think that writing good<br>
Perl does indeed require more discipline, but the power advantages<br>
(especially CPAN) help a lot.<br>
<div><div></div><div>_______________________________________________<br>
chuck-users mailing list<br>
<a href="mailto:chuck-users@lists.cs.princeton.edu" target="_blank">chuck-users@lists.cs.princeton.edu</a><br>
<a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-users</a><br>
</div></div></blockquote></div><br><br clear="all"><br></div></div><div class="im">-- <br><a href="http://michaelclemow.com/" target="_blank">http://michaelclemow.com</a><br><a href="http://semiotech.org/" target="_blank">http://semiotech.org</a><br>
<br>
</div></div>
</blockquote></div><br><br clear="all"><br>-- <br><a href="http://michaelclemow.com/">http://michaelclemow.com</a><br><a href="http://semiotech.org/">http://semiotech.org</a><br><br>
</div>
<span><chuck-session-handler_v01.zip></span>_______________________________________________<br>chuck-users mailing list<br><a href="mailto:chuck-users@lists.cs.princeton.edu">chuck-users@lists.cs.princeton.edu</a><br>https://lists.cs.princeton.edu/mailman/listinfo/chuck-users<br></blockquote></div><br></div></div></body></html>