With weinre you start a node.js debug server and add one script tag in your html. Then you start the debug client in a webkit compatible browser and finally the browser with the page you are debugging (it can be anything: mobile, remote or not).
weinre strongest points are:
- "weinre supports remote interaction, so you can run the debugger user interface on one machine and can debug a web page running on another machine. For instance, debug a web page displayed on your phone from your laptop."
- "weinre does not make use of any native code in the browser, it's all plain old boring JavaScript."
- "Because weinre doesn't use native code, the debug target code will run on browsers without specialized debug support."
Also try Live Reload[2], mentioned in the article, for a nicer editor+your_tool+browser integration.
- "LiveReload monitors changes in the file system. As soon as you save a file, it is preprocessed as needed (SASS, LESS, Stylus, Coffescript and others), and the browser is refreshed." (You don't hit reload, it uses a browser extension or a script tag)
- "LiveReload can invoke a Terminal command after processing changes. Run a Rake/Cake task, a Shell script or anything else you need."
"The remote debugging protocols are incompatible with each other, and each has a different features."
[1]http://people.apache.org/~pmuellr/weinre/docs/latest/
With weinre you start a node.js debug server and add one script tag in your html. Then you start the debug client in a webkit compatible browser and finally the browser with the page you are debugging (it can be anything: mobile, remote or not).
weinre strongest points are:
- "weinre supports remote interaction, so you can run the debugger user interface on one machine and can debug a web page running on another machine. For instance, debug a web page displayed on your phone from your laptop."
- "weinre does not make use of any native code in the browser, it's all plain old boring JavaScript."
- "Because weinre doesn't use native code, the debug target code will run on browsers without specialized debug support."
Also try Live Reload[2], mentioned in the article, for a nicer editor+your_tool+browser integration.
[2]http://livereload.com/
- "LiveReload monitors changes in the file system. As soon as you save a file, it is preprocessed as needed (SASS, LESS, Stylus, Coffescript and others), and the browser is refreshed." (You don't hit reload, it uses a browser extension or a script tag)
- "LiveReload can invoke a Terminal command after processing changes. Run a Rake/Cake task, a Shell script or anything else you need."