00:12 <GitHub107> [opal-jquery] rubys opened pull request #25: untaint path (master...safe_path) http://git.io/ad4lmw

02:04 <cliffstah> hey there

02:04 <cliffstah> first off - fantastic job.. I've needed several new pairs of trousers since I discovered Opal.

02:06 <cliffstah> second, I'm trying to do some funky things with it over at Koding.com. Their KD Apps API uses Node and CoffeeScript, and well, being a complete Ruby fanatic I'd rather use that. So I'm trying to put together an alternative "compiler" using Opal, but there are a couple of things I haven't quite figured out and I wondered if someone could spare me a moment to assist :-)

02:07 <cliffstah> It's really quite simple and I'm sure that you could point me in the right direction rather quickly. (incidentally, if you want to try Koding.com out - please let me give you a referrer link so I can earn a little disk space in the process - thanks!)

02:08 <cliffstah> Anyway, I digress. What I'm trying to do, is stick as close as I can to the Koding eco system, i.e. node, and gently crowbar this alternative "compiler" in. This basically means using npm rather than gem. From what I can see, opal-node is the interpreter side of Opal, and the compiler itself is a gem. Is it possible to compile using opal-node, or should I be looking at perhaps taking the output of the opal gem and using that in my node module?

02:10 <cliffstah> Thanks in advance if you happen to see this before I eventually and invariably work it out, and thanks anyway if not ;-)

02:29 <cliffstah> oh my word. so, if I have this right.. you have a Ruby parser/compiler.. that can compile _itself_ into JS..?

02:29 <cliffstah> that.. I need more trousers.