Thank you for all the good advice! I've installed the DebugBar, agree with mrpollo about the ie developer toolbar (I can't find a script console in there, but can edit CSS .... are they dishing out separate versions??) - and, not having seen the new 'Visual Express' thingies, am now all excited about brushing up on my VB (last used circa 1998)
Much more of this, I might even learn to code ;) Thanks again, Cherry On Apr 21, 8:56 pm, "Jeffrey Kretz" <[EMAIL PROTECTED]> wrote: > You may not want to go through the trouble, but the free Visual Studio Web > Express 2008 has an excellent debugger. > > http://www.microsoft.com/express/download/#webInstall > > Now, I still prefer Firefox for its DOM/CSS inspectors and NET traffic > analysis, but the actual debugging tools in the VS product are much better > than those in Firebug, it has excellent breakpointing, variable inspection, > etc, etc. > > JK > > -----Original Message----- > From: jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] On > > Behalf Of mrpollo > Sent: Monday, April 21, 2008 12:13 PM > To: jQuery (English) > Subject: [jQuery] Re: IE debugging advice, please > > dude perhaps the only good valid solution that microsoft has given is > the ie developer toolbar > > http://www.microsoft.com/downloads/details.aspx?familyid=e59c3964-672... > bb3e-2d5e1db91038&displaylang=en > > its obviously not firebug, but its a good try, no on the fly css > editing, but you get this cool inspect tool just like the one firebug > has > plus the dom tree inspector which is always good to have, tons of > other stuff i dont really use > but its a good solution in my opinion > > On Apr 20, 7:42 pm, "[EMAIL PROTECTED]" > <[EMAIL PROTECTED]> wrote: > > As I stumble towards discovery of jQuery and all things Javascript, I > > frequently get knocked down by IE ;) It throws fatal errors far more > > often than Firefox (whose debugger I can understand) but IE's debug > > option invariably points to an 'error' in the jQuery core. I assume > > that's not the *real* error; just the point in the main script at > > which *my* script caused a fault. > > > Please could someone point me towards a better debugger for ie? > > I should emphasise that I really am floundering in the dark here. > > Ideally, I need something dead simple. I can't even use Firebug > > properly! > > > Any & all advice much appreciated, as ever :) > > Cherry.
