Without making any bindings to Jitter et al, it would be pretty
straightforward. Just build the ruby interpreter into an external
object and create some mechanism for loading scripts and talking to
inlets and outlets. Check out the Ruby C interface for more details
on how to do this:
i've considered doing that, but it feels like that might be one too many levels of indirection. it'd be nice to not have to bridge it through another language. then again, perhaps that doesn't really matter.
thanks for the suggestion.