check type of param in display()
refactor result printing from evalIn*Scope over to routines in venkman-handlers.js
add refreshResultsArray() to call refresh() on all elements of the $ array
add new exception number
seperate VAL message types into WORD and VAL, VAL messages are words surrounded in <>, used as a variable name in a text message, WORD messages are single (well, no more than a few) words usually replaced into longer messages.
added more strings
remove the "/" before commands. No reason to use "/where" over just "where" in a debugger
implement evald, props, and propsd commands
s/VAL/SCOPE/ where appripriate
remove unused parameter from quit and where
add pgup and pgdn handkers
add tons of .js files for drag-and-drop and tooltips support
add tooltip popupset
switch from an html:iframe (which supports .contentDocument) to a xul:iframe (which supports tooltips and dnd)
promote console.display() to display()
add displayCommands(), evalInDebuggerScope(), evalInTargetScope(), fillInToolTip() [copied from chatzilla], formatEvalException() [refactored from venkman-handlers.js]
set window._content for drag-and-drop foo
call displayCommands() on startup.
add "venkman-link" to CSS class in htmlVA() for the case where the caller is providing custom attributes that do not include "class"
don't print usage if a command returns false, that's lame
imeplement /commands, /cont
factor exception formatting into formatEvalException now that there are two places that need it
make onInputEval evaluate in the target scope instead of the debugger's scope
copy tab complete code from chatzilla
add htmlVA() to create anchors with the "venkman-link" class
print hello message on successful startup, with link to sample debug target.
add exception IDs missing parameter, invalid parameter, and subscript load exceptions
add function name property to BadMojo objects
throw invalis parameter from display() if the parameter looks bad.
switch from document.createElementNS to the new html utility functions.
allow message to be a string (we create the testnode), or a DOM object (we just append it to the content tree)
remove sample output
s/console.commands/console._commands/g, leading _ indicates variable is "private"
l10n in onInputCommand()
report function name for caught exceptions, if it is available
implement /frame, /help, /scope, /quit, and /where