4 ms·
A bit off topic: what is your interactive JS sandbox? (Firebug, Chrome console, Rhino... ?)
by ez77 16y ago
A bit off topic: what is your interactive JS sandbox? (Firebug, Chrome console, Rhino... ?)
- nfriedly 16y agoFirebug for something quick, Rhino for something that is repeated often enough to be scripted. Occasionally Chrome's built-in console, but I just don't like it it as much as firebug. I've played with node.js a bit, but when I toyed with it it wasn't anywhere near production ready. (This was over a year ago, I might come back to it again sometime soon.)
- sjs 16y agoMost of the time I use Chrome's console and node in a terminal. If I'm in Emacs I might fire up swank-js[1] which lets me interact with standalone JS interpreters like v8 and Rhino, but also contains a server that bridges the gap between the major browsers. Simply open up a web page in Firefox, Safari, Chrome, or Opera and then interact with that browser's JS engine from Emacs. [1] https://github.com/ivan4th/swank-js https://github.com/ivan4th/swank-js
- paulirish 16y agohttp://tutti.tobyho.com http://tutti.tobyho.com is definitely the finest. You get an interactive console, and you get results from all browsers you want to test, immediately.
- amadeus 16y agoAnother really great tool is http://jsfiddle.net http://jsfiddle.net It allows you to mock up quick examples/bugs/etc.