Hey, I just found this:
http://wiki.cs.princeton.edu/index.php/ChucK/Dev/Shell/doc#Command_Summary
I don't know if it had ever been discussed (documented? ha!), but
check out "Inline Coding." With a solid pre-made library of static
class values that could be shared globally this could make for actual
livecoding. It still doesn't help with your want for VIM, but it would
be even more badass to just livecode with a huge terminal window and
nothing else. The audience doesn't have to know that the classes
you're calling are homemade, nor will they care, unless they're total
nerds, which most of them and us probably are. It's like when Thurston
Moore comes on stage with a power drill to play a guitar solo--we
don't think, "Man, he should have built that power drill ON STAGE from
scratch," we think, "Rad."
Andrew
On Fri, Sep 11, 2009 at 11:23 AM, Kassen
Andrew;
I'm not sure why using the shell makes a huge difference, aside from avoiding the mouse.
I'd like to make a distinction here, before the poor mice and touchpads all get put against the wall; I think the ideal editor wouldn't *need* the use of a mouse, this is distinct from offering support for it. Nearly all good code editors these days can make use of the mouse if we'd like but don't need it if we don't want to.
Kas. _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users