On Thu, 20 May 2004 14:40:36 -0700 (PDT), Amy Alexander wrote
> ok, so here's my 2-part question, for you and alex and everyone:
>
> 1) how do you go about telling the interpreter "execute now" when
> live coding? dave, you're using highlighting? does it execute as
> soon as you highlight? or you have to hit RETURN or something?
Yep, you have to hit F5 - in maya it's the enter key on the keypad, but on a
laptop (which I have) that's more tricky :)
If no code is selected, hitting F5 will execute the whole script BTW.
Also in fluxus you can set a bit of code that's called each frame - if you
make this a function call, you can modify the function, highlight and execute
the scheme function definition again, and it will update live.
I also made a simple gui (sorry ;)) that just consists of buttons that execute
code snippets (again, usually function calls, but it can be whatever you want)
Again, you can build this simple gui live, or load it from prebuilt scripts.
> i'm for now using the semicolon (which lingo does not use) to
> indicate to lingo "execute this now!" but i'm wondering if there's a
> better way than using a character or even RETURN within the "editor"
> - since any of these are subject to typos, and then i have to delete
> it to edit the line to make it do something else, and sometimes i
> forget and it tries to execute an incomplete line of code. i realize
> this will vary with the livecoding methodology being used, but just
> curious how others are doing this.
As long as you don't stop running the visuals, script errors should not be a
problem.
> 2) validation - i make typos when livecoding, and then the illegal
> commands generate a
> nasty crash or at least an error in performance! i may just
> integrate those into the performance, but, curious how others
> handling this problem? are you having some code validation go on
> before execution, or... ???
No crashes. Well, that's the idea anyway - I keep everything really simple, I
have a few issues with the physics library (which is superb in other respects:
http://www.ode.org/) but I've got them mostly under control now.
For script errors the lower area of the window spews them out. with scheme
it's mostly mismatching (((()))) so I added parentheses highlighting in the
editor which makes it miles easier.
cheers,
dave
................................. www.pawfal.org/nebogeo
Received on Fri May 21 2004 - 10:48:41 BST