factor step and continue commands.
Toggle script list mode (short name/ full url) on column header click
fix bug focusing a source file more than once
enable UI for debug commands onDebugTrap
adding support for source, stack, and script list outliners.
include venkman-outliners.js in the party.
add the three outliners mentioned above, with splitters and grippies and all that jazz.
adding support for source, stack, and script list outliners.
add startupTests() function to run a few tests on startup.
add cont() to continue from a debugTrap()
add focusSource() to bring a filename/linenumber up in the source text outliner
fix window._content code in init()
add const for "no stack" error
adding support for source, stack, and script list outliners.
add onDebugTrap and onFrameChanged handlers, to be called by debugger.js when something happens that the UI might want to know about.
moved breakpoint related display()s into debugger.js
refactored break, clear, fbreak, and fclear command handlers to use set[Future]Breakpoint()
added handlers for clicks on the three outliners
adding support for source, stack, and script list outliners.
moved breakpoint related status display()s from handlers.js to here, to that you get console feedback when you set a breakpoint with the UI.
moved initDebugger() and attachDebugger() to the top of the file.
add setCurrentFrameByIndex(), clearCurrentFrame(), getCurrentFrameIndex(), and getCurrentFrame(), migrated code that accessed console._currentFrameIndex to these functions.
make setBreakpoint() smarter (it doesn't blindly clear any breakpoints before setting the new one anymore. that spewed extra "clearing breakpoint" "setting breakpoint" messages. now we scan the breakpoint list ourselves for dupes.)
bug 82462, break in scripts that arent loaded yet
move console._scripts/_sources creation into initDebugger()
check to see if we need to set a breakpoint when new scripts are loaded
add some comments to initDebugger()
implement isFutureBreakpoint() and setFutureBreakpoint()
enumerate existing scripts on load for the case where the user has js.debugger.autoload set. This will allow for the setting of breakpoints in scripts that were loaded before the debugger.
use (a modified copy of chatzilla's) munger on output text instead of the one-off hardcoded line break code that was here.
add rules for hyperlinks and long word breaking to munger
implement matchFileName()
add stringToDOM() to turn a string into DOM nodes via the munger
add ERR_FAILURE exception type
list breakpoints if not data given tot he break command
factor filename matching code into matchFileName()
add clear command to clear breakpoints by file/line number, or breakpoint id
show source text when changing frames
add console._sources object to hold source text
clear breakpoints associated with a script when the script is deleted
show source text when the debugger stops
add findNextExecutableLine (Not done, not used)
add loadSource(), displaySource(), getBreakpoint(), clearBreakpoint(), clearBreakpointByNumber() functions
store fileName and line in breakpoint object
