Javascript Exploration With jfiddle.net and Chrome Debugger
jfiddle user interface |
Now I can do fast iterative cycles. Change some HTML, retry; change some CSS, retry; change some javascript, retry. All nicely partitioned and ready to be put in a module file.
If I use jQuery(edge) theory says that I can also add jQuery Lint with a click of a button. jQuery Lint is a nice idea: it will give you meaningful console messages for jQuery misuse. Like this:
jQuery Lint messages |
jQuery Lint details |
And I can expand the second "more info" and find out how I might remedy the problem:
jQuery Lint remedies |
I think that for now Chrome is the way. I need to clean up my environment so that I don't see so many plugin scripts and that will be alright.
Comments
Post a Comment