There's a watchlist where you can set up global variables to watch; but there's no need to do this with local variables, which appear and disappear in the local pane as they are defined or go out of scope. The variables in this pane are tree-structured: you can go to a variable holding the return of an XMLrequest and inspect the entire DOM. I was particularly pleased with the inclusion of a current variable pane, which provides a scrolling window to display a single variable; I found this very useful when trying to inspect long strings holding HTML or XML source. The debugger also allows you to hover over any variable in the code to inspect its value.
Installation was simple and straightforward. But after I installed, I was unable to get the app to stop at breakpoints to allow me to debug. I wrote Splinetech support, and got a prompt reply asking for my Windows and IE versions. Within twenty-four hours I was issued a new Splinetech executable where the problem was solved.
One limitation of the program is that it works only with HTML web pages. Pages that were produced by server scripts - such as php or ASP pages, must be captured by viewing the page source and saved as HTML before debugging. This works fine, but it adds a step to the debug-edit-run cycle. Your instinct is to edit the page in the debugger directly. But instead, you need to edit the asp file, launch it, and recapture it as HTML. I got into a cycle of working and editing in the static page for a while, then copying the changes over to the ASP page. It would be very nice to have all of this automated some way.