[EMAIL PROTECTED] wrote: > Isn't this what the scriptor engine is all about?
The scriptor could be immensely useful here. > I like the idea of getting ruby into this. I don't really mind what the scriptor ends up being coded in, but if I'm going to personally implement it, I'm going with elastiC. But if anyone else wants to step in to code it in Ruby, he/she will have my full cooperation, and I'll _gladly_ yield the task of implementing it. It isn't rocket science, only a few tricky parts, but I simply have very little time available. [ 67 lines snipped, tsk tsk ] Emile --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
