env.js

17 views

Skip to first unread message

Edward Blackburn

unread,

Jun 18, 2011, 2:39:44 PM6/18/11

to IronJS

Hi,

Well, wow! Seriously impressed so far. May I enquire, what effort is
required to implement hosting env.js? Is this part of a roadmap? Is
this even desirable?

My initial thought when I first saw IronJS, was can I hook IronJS up
with sizzle.js so I can get CSS selectors on the server side instead
of slaving over XPath? If IronJS could implement / host env.js I could
conceivably run my qunit and other javascript tests server side on the
CI server without mandating Webdriver or similar. I appreciate that
there are headless browser options, I just favour a simpler, smaller,
light weight solution such as IronJS.

Keep up the good work chaps.

Ed

Fredrik Holmström

unread,

Jun 19, 2011, 6:29:46 AM6/19/11

to Edward Blackburn, IronJS

Hey!

Thanks for all the kind words!

I'm sorry to say that implementing something as specific as env.js, the DOM etc. is not on the roadmap for IronJS.

IronJS is a javascript runtime, in the same way that V8 is the runtime used in Chrome. The runtime itself doesn't

supply anything other then the language + the built in objects and functions.

Anything external like env.js, the DOM, a html rendering engine, css selectors, etc. is all built outside the runtime

and then injected into it.

Regards,
Fredrik Holmström