5 ms·
Absolutely Awesome! One more thing is needed, however. The ability to be able to save the modified sources to the server (with appropriate security of course, d
by ypcx 15y ago
Absolutely Awesome! One more thing is needed, however. The ability to be able to save the modified sources to the server (with appropriate security of course, dev-env only). Also the ability to fetch the server sources from the server, if e.g. I'm running a Node.js and I want to debug and edit the JS in Chrome - along with the client side JS, side by side.
The close we programmers are to the "living code", the better. The file-watching, auto-reloading and re-executing BDD's (or TDD's, etc.) like vows (http://vowsjs.org/ http://vowsjs.org/) get pretty close to it, but it's not the same.
When I'm coding a function, I want to be able to run it anytime (when the syntax is OK of course), and in the environment of my program.
Great stuff. Also similar in-client code editing efforts, Firefox: https://github.com/Gozala/sky-edit https://github.com/Gozala/sky-edit, general: https://github.com/ajaxorg/ace https://github.com/ajaxorg/ace
- elijahmanor 15y agoYou are in luck! There is an autosave Chrome extension that will save any changes you've made to the JavaScript or CSS from Dev tools to your local file system... http://addyosmani.com/blog/autosave-changes-chrome-dev-tools/ http://addyosmani.com/blog/autosave-changes-chrome-dev-tools...
- adam-a 15y agoNot exactly side by side, but Node Inspector lets you use the webkit debug tools to step through Node.js code. https://github.com/dannycoates/node-inspector https://github.com/dannycoates/node-inspector