ow yeah! nice idea Kassen. That, with Std.system to execute the command line can make it all somehow self-contained. something like:<br><br>// self-contained filenames chuck access<br>Std.system("chuck my-engine:filename1:filename2:filename3...")<br>
<br>which, when sporked, calls <a href="http://my-engine.ck">my-engine.ck</a> with the filenames of a directory all accessible by me.arg<br>clearly, "filename1:filename2:filename3" can be replaced by a related command line for the given OS.<br>
<br>just sharing.. cheers<br><br><br><br><div class="gmail_quote">2008/6/8 Kassen <<a href="mailto:signal.automatique@gmail.com">signal.automatique@gmail.com</a>>:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
2008/6/8 Renato Fabbri <<a href="mailto:renato.fabbri@gmail.com" target="_blank">renato.fabbri@gmail.com</a>>:<br><div class="gmail_quote"><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Kassen,<br><br>okay, meanwhile one can stick to python scripts and osc messages when necessary. any better idea?<br></blockquote></div><div><br>I don't know if it's "better" but anything that can get a list of files in a dir, like BASH scripting or the Windows commandline "for" command (to loop over file names) could call a .ck file with those names as parameters? That would remove the OSC part and thus reduce complexity. I'm making this up on the spot, it may or may not be practical.<br>
<br>Kas.<br></div></div><br>
<br>_______________________________________________<br>
chuck-users mailing list<br>
<a href="mailto:chuck-users@lists.cs.princeton.edu">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>
<br></blockquote></div><br>