webmonkey.com — Writers edit, architects redraw, and programmers debug. Development environments are usually nice enough to give programmers a bunch of tools to help determine where their program's going wrong. But with JavaScript, your development environment is a web browser, and things aren't quite so hospitable.
May 10, 2006 View in Crawl 4
bubbles2112May 10, 2006
that's a good article right there.
coolhanlukeMay 11, 2006
I may be a noob programmer, but Visual Studio / Visual Basic for Applications, has a remarkable debugger. Break-points, watches, intellisense, and pre-compile syntax checks make coding in VB a breeze. If there is a similar editor for Java / Javascript, let me know!Ok. VB programming jokes commence... now.
jull1234May 11, 2006
This article is crap. Its like explaining the printf function as "basic debugging in C" I was hoping for something a bit more useful.
tablatronixMay 11, 2006
what i want to know is how do you debug document.write ? write it to a textfield ?
willcode4beerMay 11, 2006
Looks like someone beat me to an even better (read simpler) solution.function setCssClass(node,className){ node.setAttribute("class",className,0); node.setAttribute("className",className,0);}
natehopMay 12, 2006
The problem here is that there aren't really any good cross browser JavaScript tools. I mean the execution path may be different in IE than FF. For example, handling of timeouts and intervals amidst other function calls. What we need are good tools that allow us to quickly and easily see the differences in browser execution of the same code.One tool that I use daily for this is jsTracer. <a class="user" href="http://jstracer.sourceforge.net/">http://jstracer.sourceforge.net/</a>jsTracer is a simple to use cross browser JavaScript tracing and logging tool. One very nice feature is that you can collect stack information on the functions you are tracing which helps to narrow down the potential problem spots, allowing you to focus your tracing and debugging efforts where you need it.Of course I'm biased because I wrote the tool, primarily out of frustration that there wasn't something already available for me to use that met my needs.