make dump tree function taka a param
remove bogus _cache dance
add matchesScriptRecord method to breakpoint record
only do the icode replacement if the breakpoint is enabled in addScriptRecord
change string concats to getMsg calls, to make bidi more better
don't duplicate setBreakpoints()s efforts by checking for matching files in onInputBreak
reimpliment onInputFBreak
remove onInputFClear. future breakpoints can now be cleared wit the standard clear command.
remove dead onScriptCreated function
dont pay attention to scripts without filenames
remove script from the script tree when it is unloaded
if a newly created script matches an existing breakpoint record, add that script to the breakpoint record.
remove obsoleted future breakpoint functions
add css for new step out, step over, stop buttons
change continue and step in commands to use the new png images
add css for breakpoint, script, and watch views
implement next, step out, and stop state commands
bring breakpoint implementation in line with the new breakpoint and script views
add destroy() method to tear down the debugger
add styles for executable/not executable lines in the source code window.
add style for exception trace messages.
color stop (red) and continue (green) messages so they're easy to spot.
decrement console._stopLevel in cont() and step() functions, like good little boys and girls
initDebugger *after* setting up the console routines, we'll need them
set up the excetions submenu checkmarks correctly onCreate
load the source if it's not there in onDebugTrap
add onDebugContinue to clear our state when we continue
implement tmode command
move onclose back to onunload, onclose doesn't fire if the user selects "Quit" from the file menu.
add tmode command to trace/ break when the target throws an exception.
fix "breakpoint hit while servicing breakpoint" behavior. When we hit the second breakpoint, its stack is put on top of the current stack. Not the best solution, but better than leaving the user in an undefined state.
distunguish between executable and non-executable lines in the source array so we can distinguish the lines in CSS.
expand tabs in the source (outliner doesn't know what to do with \t.)
if we can't load a source file sync, try it async.
s/throw BadMojo/throw new BadMojo/g so we can test with instanceof later
add formatException() function
redo BadMojo() to construct a new object, we'll need the prototype chain set up right so we can test exceptions with instanceof
catch startup exceptions and complain.
use MSG_COMMASP instead of ", "
print formatted jsdIValue in the props command's error message
detach debugger onClose instead of onUnload
implement formatArguments(), returns a strig including only the argument properties of a given jsdIValue.
made the rest of the format* functions more pro-bidi (swapped out string math in favor of format strings)
add comment to loadSource about why we use new String()
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()
rginda%netscape.com
hyatt%netscape.com
timeless%mac.com