fun with Venkman, G. Suggest, Keystrokes

[awebguynow]

still on the bandwagon to mimic Google suggest ...
although, I'd prefer to trigger off of keystrokes rather than timer
Can someone give me the skinny on whats best to use ?
onKeyPress onKeyDown onKeyUp or ??
Explain why, on 1st keystroke, textbox.value is empty, even after these
events are triggered.

Re: JS debugging and Venkman
green newbie here with this, but also had trouble with the Interactive
tab, >value
after "set as Evaluation Object" = textbox

Whats chrome:// and is this important ?
Initially I had an error involving: venkman-url-loader.js
I did install from my Win. desktop, after reading Rob Chartier's page.

Did I hear someone say Venkman works on IE ? If not, whats
equivalent.
When I include .js files in html, bring up IE, and there's an error,
the line #'s of the error, seem to be all screwy. Is there anyway to
tell, where the actual error is ?

[Thomas 'PointedEars' Lahn]

awebguynow wrote:

although, I'd prefer to trigger off of keystrokes rather than timer
Can someone give me the skinny on whats best to use ?
onKeyPress onKeyDown onKeyUp or ??
Yes.
Explain why, on 1st keystroke, textbox.value is empty, even after these
events are triggered.
That is unlikely. `onkeypress' or `onkeyup' the value should have changed.
Re: JS debugging and Venkman
green newbie here with this, but also had trouble with the Interactive
tab, >value
after "set as Evaluation Object" = textbox
Parse error.
Whats chrome://
It is the URI scheme for Gecko chrome resources. "(UI) Chrome is a generic
term to widgets and 'windows' used in a program as a container for another"
(en.Wikipedia).
and is this important ?
Depends.
Initially I had an error involving: venkman-url-loader.js
I did install from my Win. desktop, after reading Rob Chartier's page.
Uh-huh.
Did I hear someone say Venkman works on IE ?
Of course not, IE uses a completely different script engine and UI
framework.
If not, whats equivalent.
See <URL:http://jibbering.com/faq/>.
When I include .js files in html, bring up IE, and there's an error,
the line #'s of the error, seem to be all screwy. Is there anyway to
tell, where the actual error is ?

The line number, unless it is a fatal compilation error (where the line
number displayed is 0), does translate roughly to the line where the error
occurred. You have to find out the relevant resource for yourself, though,
unless you use a debugger. Welcome to the hell of Web development for IE.
PointedEars
--
What one man can invent another can discover.
-- Sherlock Holmes in Sir Arthur Conan Doyle's
"The Adventure of the Dancing Men"