hey, is there a good debugger for IE? i''ve tried searching for it, but all i can find is the windows script editor :-/ and i''m not even sure how well that works. firefox has superb stuff, but IE keeps throwing up very vague errors with perfectly valid code :-/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Hello, depending on what you want to analyze the new IE Debug Toolbar might help already: http://www.microsoft.com/downloads/details.aspx?FamilyID=E59C3964-672D-4511- BB3E-2D5E1DB91038&displaylang=en If you are really on JS only you should follow the guide here http://blogs.msdn.com/ie/archive/2004/10/26/247912.aspx that at least helps to some extend (but usability is quite low...) Another option is to google for the error. Most IE glitches are quite well documented on the net .: Fabian -----Original Message----- From: grbounce-_Pkz0AUAAAB9-VKt0-RY8LHUELm10l3Y=fabian.lange=web.de@googlegroups.c om [mailto:grbounce-_Pkz0AUAAAB9-VKt0-RY8LHUELm10l3Y=fabian.lange=web.de@google groups.com] On Behalf Of Sudhir Sent: Sonntag, 17. Juni 2007 10:43 To: Ruby on Rails: Spinoffs Subject: [Rails-spinoffs] JS debugger for IE hey, is there a good debugger for IE? i''ve tried searching for it, but all i can find is the windows script editor :-/ and i''m not even sure how well that works. firefox has superb stuff, but IE keeps throwing up very vague errors with perfectly valid code :-/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
thanks a lot... will check them out... documented? even if they''re just the usual object expected messages? On Jun 17, 2:02 pm, "Fabian Lange" <Fabian.La...-S0/GAf8tV78@public.gmane.org> wrote:> Hello, > depending on what you want to analyze the new IE Debug Toolbar might help > already:http://www.microsoft.com/downloads/details.aspx?FamilyID=E59C3964-672... > BB3E-2D5E1DB91038&displaylang=en > > If you are really on JS only you should follow the guide herehttp://blogs.msdn.com/ie/archive/2004/10/26/247912.aspx > that at least helps to some extend (but usability is quite low...) > > Another option is to google for the error. Most IE glitches are quite well > documented on the net > > .: Fabian > > -----Original Message----- > From: > > grbounce-_Pkz0AUAAAB9-VKt0-RY8LHUELm10l3Y=fabian.lange=web...@googlegroups.c > om > [mailto:grbounce-_Pkz0AUAAAB9-VKt0-RY8LHUELm10l3Y=fabian.lange=web.de@google > groups.com] On Behalf Of Sudhir > Sent: Sonntag, 17. Juni 2007 10:43 > To: Ruby on Rails: Spinoffs > Subject: [Rails-spinoffs] JS debugger for IE > > hey, is there a good debugger for IE? i''ve tried searching for it, but > all i can find is the windows script editor :-/ and i''m not even sure > how well that works. firefox has superb stuff, but IE keeps throwing > up very vague errors with perfectly valid code :-/--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Hi, These are nice (the bookmarklet idea in the third article especially), but Firebug Lite only provides the logging console from Firebug, not the javascript debugger. AFAIK, there really is nothing that comes close to Firebug''s debugger for IE, not even if you cough up for Visual Studio. Dave On Wednesday 20 June 2007 08:34, Nathaniel Brown wrote:> http://www.getfirebug.com/lite.html > http://www.phpied.com/firebug-console-for-ie/ > http://remysharp.com/2007/03/13/firebug-in-ie-for-any-web-site/ > > On 6/17/07, Sudhir <sudhir.j-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > thanks a lot... will check them out... > > > > documented? even if they''re just the usual object expected messages? > > > > On Jun 17, 2:02 pm, "Fabian Lange" <Fabian.La...-S0/GAf8tV78@public.gmane.org> wrote: > > > Hello, > > > depending on what you want to analyze the new IE Debug Toolbar might > > > help > > > already:http://www.microsoft.com/downloads/details.aspx?FamilyID=E59C39 > > >64-672... BB3E-2D5E1DB91038&displaylang=en > > > > > > If you are really on JS only you should follow the guide > > > herehttp://blogs.msdn.com/ie/archive/2004/10/26/247912.aspx that at > > > least helps to some extend (but usability is quite low...) > > > > > > Another option is to google for the error. Most IE glitches are quite > > > well documented on the net > > > > > > .: Fabian > > > > > > -----Original Message----- > > > From: > > > > > > grbounce-_Pkz0AUAAAB9-VKt0-RY8LHUELm10l3Y=fabian.lange=web...@googlegro > > >ups.c om > > > [mailto:grbounce-_Pkz0AUAAAB9-VKt0-RY8LHUELm10l3Y=fabian.lange=web.de@g > > >oogle groups.com] On Behalf Of Sudhir > > > Sent: Sonntag, 17. Juni 2007 10:43 > > > To: Ruby on Rails: Spinoffs > > > Subject: [Rails-spinoffs] JS debugger for IE > > > > > > hey, is there a good debugger for IE? i''ve tried searching for it, but > > > all i can find is the windows script editor :-/ and i''m not even sure > > > how well that works. firefox has superb stuff, but IE keeps throwing > > > up very vague errors with perfectly valid code :-/-- Author: Prototype & Scriptaculous in Action, Ajax in Practice, Ajax in Action --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
http://www.getfirebug.com/lite.html http://www.phpied.com/firebug-console-for-ie/ http://remysharp.com/2007/03/13/firebug-in-ie-for-any-web-site/ On 6/17/07, Sudhir <sudhir.j-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > thanks a lot... will check them out... > > documented? even if they''re just the usual object expected messages? > > On Jun 17, 2:02 pm, "Fabian Lange" <Fabian.La...-S0/GAf8tV78@public.gmane.org> wrote: > > Hello, > > depending on what you want to analyze the new IE Debug Toolbar might help > > already:http://www.microsoft.com/downloads/details.aspx?FamilyID=E59C3964-672... > > BB3E-2D5E1DB91038&displaylang=en > > > > If you are really on JS only you should follow the guide herehttp://blogs.msdn.com/ie/archive/2004/10/26/247912.aspx > > that at least helps to some extend (but usability is quite low...) > > > > Another option is to google for the error. Most IE glitches are quite well > > documented on the net > > > > .: Fabian > > > > -----Original Message----- > > From: > > > > grbounce-_Pkz0AUAAAB9-VKt0-RY8LHUELm10l3Y=fabian.lange=web...@googlegroups.c > > om > > [mailto:grbounce-_Pkz0AUAAAB9-VKt0-RY8LHUELm10l3Y=fabian.lange=web.de@google > > groups.com] On Behalf Of Sudhir > > Sent: Sonntag, 17. Juni 2007 10:43 > > To: Ruby on Rails: Spinoffs > > Subject: [Rails-spinoffs] JS debugger for IE > > > > hey, is there a good debugger for IE? i''ve tried searching for it, but > > all i can find is the windows script editor :-/ and i''m not even sure > > how well that works. firefox has superb stuff, but IE keeps throwing > > up very vague errors with perfectly valid code :-/ > > > > >-- Nathaniel Steven Henry Brown Toll Free: 1-877-446-4647 Vancouver: 604-724-6624 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Hi Ryan,
Good point - I''ve seen the express vis studio editions, didn''t
make the
connection. It''s a pretty big download/install for a debugger, but hard
disks
and bandwidth are cheap these days, I guess!
I''m currently using the Script Editor that comes with FrontPage 2003
(same
thing that ships with VS 2003, I think? I hasten to add that I don''t
use
Front Page for anything else, it''s just the cheapest route to getting
the
script editor that I knew of!).
Anyway, the one thing that really limits script editor''s usefulness to
me (and
the freebie debugger is the same in this respect) is that the
breakpoint-setter doesn''t understand inline function definitions, e.g.
01 function blah(){
02 new Ajax.Request(
03 myURL,
04 { method: "POST",
05 onComplete:function(xhr){
06 var responseObj=Object.toJSON(xher.responseText);
07 doSomething(responseObj.this);
08 doSomethingElse(responseObj.that);
09 }
10 }
11 );
12 }
stopping me from setting breakpoints on lines 6-8 interactively, which, in an
Ajax app, is usually where a lot of the interesting stuff is going on. Worse,
when I define a JS object type using Class.create() and the
MyObjectType.prototype={ } approach, every method of the object is an inline
function declaration, hence inaccessible to the debugger''s breakpoint
mechanism. The whole P&S coding style is geared around inline functions, and
not for trivial, stylistic reasons either. That functional-style programming
approach has a very natural fit to JS as a language, and I''d be loath
to give
it up these days.
I can add a "debugger;" statement to my code within lines 6-8 and
reload the
app, but that''s kind of tedious and defeats the immediacy of the
interactive
debugger. I could also stop defining functions inline, and pass references to
top-level functions, but that would make my code look like death warmed up.
OK, this is starting to sound like a rant - I''m not venting my spleen
at you,
Ryan. You''ve got the VWD installed already, and say you like it. Does
the
VWD debugger understand inline function declarations in the way I''ve
described (a basic prerequisite for being ''capable'' IMO)? If
so, I''ll happily
burden my machine with it''s 300MB presence and abstain from saying rude
things about MS tools for, ooh, a whole day at least.
TIA
Dave Crane
On Wednesday 20 June 2007 15:02, Ryan Gahl wrote:> You can get VWD (Visual Web Developer) Express from MS for free, which is
> basically VS pared down. That has excellent js debugging. Yes, I use
> firebug all the time, and love it. But yes, the js bebugging in VWD is far
> faster and more capable. I use firebug for FF dev, VWD for IE dev.
>
--
Author: Prototype & Scriptaculous in Action, Ajax in Practice, Ajax in
Action
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
You can get VWD (Visual Web Developer) Express from MS for free, which is basically VS pared down. That has excellent js debugging. Yes, I use firebug all the time, and love it. But yes, the js bebugging in VWD is far faster and more capable. I use firebug for FF dev, VWD for IE dev. On 6/19/07, Dave Crane <dave-Sy7q136SasSXmMXjJBpWqg@public.gmane.org> wrote:> > > Hi, > > These are nice (the bookmarklet idea in the third article especially), but > Firebug Lite only provides the logging console from Firebug, not the > javascript debugger. AFAIK, there really is nothing that comes close to > Firebug''s debugger for IE, not even if you cough up for Visual Studio. > > Dave > > On Wednesday 20 June 2007 08:34, Nathaniel Brown wrote: > > http://www.getfirebug.com/lite.html > > http://www.phpied.com/firebug-console-for-ie/ > > http://remysharp.com/2007/03/13/firebug-in-ie-for-any-web-site/ > > > > On 6/17/07, Sudhir <sudhir.j-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > thanks a lot... will check them out... > > > > > > documented? even if they''re just the usual object expected messages? > > > > > > On Jun 17, 2:02 pm, "Fabian Lange" <Fabian.La...-S0/GAf8tV78@public.gmane.org> wrote: > > > > Hello, > > > > depending on what you want to analyze the new IE Debug Toolbar might > > > > help > > > > already: > http://www.microsoft.com/downloads/details.aspx?FamilyID=E59C39 > > > >64-672... BB3E-2D5E1DB91038&displaylang=en > > > > > > > > If you are really on JS only you should follow the guide > > > > herehttp://blogs.msdn.com/ie/archive/2004/10/26/247912.aspx that at > > > > least helps to some extend (but usability is quite low...) > > > > > > > > Another option is to google for the error. Most IE glitches are > quite > > > > well documented on the net > > > > > > > > .: Fabian > > > > > > > > -----Original Message----- > > > > From: > > > > > > > > grbounce-_Pkz0AUAAAB9-VKt0-RY8LHUELm10l3Y> fabian.lange=web...@googlegro > > > >ups.c om > > > > [mailto: > grbounce-_Pkz0AUAAAB9-VKt0-RY8LHUELm10l3Y=fabian.lange=web.de@g > > > >oogle groups.com] On Behalf Of Sudhir > > > > Sent: Sonntag, 17. Juni 2007 10:43 > > > > To: Ruby on Rails: Spinoffs > > > > Subject: [Rails-spinoffs] JS debugger for IE > > > > > > > > hey, is there a good debugger for IE? i''ve tried searching for it, > but > > > > all i can find is the windows script editor :-/ and i''m not even > sure > > > > how well that works. firefox has superb stuff, but IE keeps throwing > > > > up very vague errors with perfectly valid code :-/ > > -- > Author: Prototype & Scriptaculous in Action, Ajax in Practice, Ajax in > Action > > > >-- Ryan Gahl Manager, Senior Software Engineer Nth Penguin, LLC http://www.nthpenguin.com -- Architect WebWidgetry.com / MashupStudio.com Future Home of the World''s First Complete Web Platform -- Inquire: 1-262-951-6727 Blog: http://www.someElement.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Hi Ryan, Oh well, that''s a shame, I was hoping to be proven wrong on this one :) I like the AnonymousDebug() function - lets you add the breakpoints without having to add debugger; statements into the code. But in a complex script, wouldn''t you need several of these to avoid the breakpoint getting triggered whenever _anything_ happens, if you have lots of calls to it peppeed through the code. And if you need to uncomment the calls to the anon debug fn, you''re back to writing "debugger;" statements. I''ll give it a try anyway, and see what it feels like in practice. Cheers, Dave On Thursday 21 June 2007 15:37, Ryan Gahl wrote:> Very real concerns, Dave. Yep, I code js the same way, and use anonymous > functions all over the place. There are some places where you''re right, you > need a debug anchor to make a deep function line breakable. The standard > way of defining method, as you describe, though works fine in VWD. So yes, > I''ve learned to live with the fact that if I want to step through some > functions, I need to place a debug anchor method call at the beginning... > > For example: > > test = Class.create(); > test.prototype = { > initialize: function() { > //lines in here are breakpoint enabled > }, > > test: function() { > //same with this function > }, > > test2: function() { > var someArray = [1,2,3,4,5]; > someArray.each(function(num) { > //trying to place a breakpoint in here results in the script > breaking no within the anonymous function, but at the point the .each() > method is called > }); > } > } > > > So, the way to be able to step through those types of functions is to have > some generic empty method at a higher level (global is fine), place a > breakpoint within it, then call that function from within the anonymous > function you want to step through... > > function AnonymousDebug() { > //place breakpoint on this line > } > > ...within test2() from the example above... > someArray.each(function(num) { > AnonymousDebug(); > //when it breaks within that anchor function, you can then hit F11 > to step into this function > }); > > > So, as mentioned, ''tis not ideal, but you can workaround things. As I > understand, the script debugging facilities shipping with the next version > ("Orcas") handles anonymous debugging much better. > > The question was, "what''s the best tool available for free to debug js in > IE".... VWD is it, and this is how... :-) > > Oh, also, while debugging, in VWD you can go to "Debug > Windows > Script > Explorer" to see the list of currently loaded script, including eval''ed > code, which you can use to place breakpoints in and step through, which is > something firebug doesn''t let you do. So, right now, it''s a trade off for > sure. > > On 6/20/07, Dave Crane <dave-Sy7q136SasSXmMXjJBpWqg@public.gmane.org> wrote: > > Hi Ryan, > > > > Good point - I''ve seen the express vis studio editions, didn''t make the > > connection. It''s a pretty big download/install for a debugger, but hard > > disks > > and bandwidth are cheap these days, I guess! > > > > I''m currently using the Script Editor that comes with FrontPage 2003 > > (same thing that ships with VS 2003, I think? I hasten to add that I > > don''t use Front Page for anything else, it''s just the cheapest route to > > getting the script editor that I knew of!). > > > > Anyway, the one thing that really limits script editor''s usefulness to me > > (and > > the freebie debugger is the same in this respect) is that the > > breakpoint-setter doesn''t understand inline function definitions, e.g. > > > > 01 function blah(){ > > 02 new Ajax.Request( > > 03 myURL, > > 04 { method: "POST", > > 05 onComplete:function(xhr){ > > 06 var responseObj=Object.toJSON(xher.responseText); > > 07 doSomething(responseObj.this); > > 08 doSomethingElse(responseObj.that); > > 09 } > > 10 } > > 11 ); > > 12 } > > > > stopping me from setting breakpoints on lines 6-8 interactively, which, > > in an > > Ajax app, is usually where a lot of the interesting stuff is going on. > > Worse, > > when I define a JS object type using Class.create() and the > > MyObjectType.prototype={ } approach, every method of the object is an > > inline > > function declaration, hence inaccessible to the debugger''s breakpoint > > mechanism. The whole P&S coding style is geared around inline functions, > > and > > not for trivial, stylistic reasons either. That functional-style > > programming > > approach has a very natural fit to JS as a language, and I''d be loath to > > give > > it up these days. > > > > I can add a "debugger;" statement to my code within lines 6-8 and reload > > the > > app, but that''s kind of tedious and defeats the immediacy of the > > interactive > > debugger. I could also stop defining functions inline, and pass > > references to > > top-level functions, but that would make my code look like death warmed > > up. > > > > OK, this is starting to sound like a rant - I''m not venting my spleen at > > you, > > Ryan. You''ve got the VWD installed already, and say you like it. Does > > the VWD debugger understand inline function declarations in the way I''ve > > described (a basic prerequisite for being ''capable'' IMO)? If so, I''ll > > happily > > burden my machine with it''s 300MB presence and abstain from saying rude > > things about MS tools for, ooh, a whole day at least. > > > > TIA > > > > Dave Crane > > > > On Wednesday 20 June 2007 15:02, Ryan Gahl wrote: > > > You can get VWD (Visual Web Developer) Express from MS for free, which > > > > is > > > > > basically VS pared down. That has excellent js debugging. Yes, I use > > > firebug all the time, and love it. But yes, the js bebugging in VWD is > > > > far > > > > > faster and more capable. I use firebug for FF dev, VWD for IE dev. > > > > -- > > Author: Prototype & Scriptaculous in Action, Ajax in Practice, Ajax in > > Action-- Author: Prototype & Scriptaculous in Action, Ajax in Practice, Ajax in Action --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Ryan, How do you get the VWD debugger to kick in when you''re not doing an ASP.Netwebsite using cassani? I''ve had it kick in when i get a script error and i''m in ''debug mode'' for the website, (ie i can stop on breakpoints etc) but never seen it fire when ie throws a script error (say im running a .html file which is a sandbox for some js development) Gareth On 6/21/07, Ryan Gahl <ryan.gahl-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > You can get VWD (Visual Web Developer) Express from MS for free, which is > basically VS pared down. That has excellent js debugging. Yes, I use firebug > all the time, and love it. But yes, the js bebugging in VWD is far faster > and more capable. I use firebug for FF dev, VWD for IE dev. > > On 6/19/07, Dave Crane <dave-Sy7q136SasSXmMXjJBpWqg@public.gmane.org> wrote: > > > > > > Hi, > > > > These are nice (the bookmarklet idea in the third article especially), > > but > > Firebug Lite only provides the logging console from Firebug, not the > > javascript debugger. AFAIK, there really is nothing that comes close to > > Firebug''s debugger for IE, not even if you cough up for Visual Studio. > > > > Dave > > > > On Wednesday 20 June 2007 08:34, Nathaniel Brown wrote: > > > http://www.getfirebug.com/lite.html > > > http://www.phpied.com/firebug-console-for-ie/ > > > http://remysharp.com/2007/03/13/firebug-in-ie-for-any-web-site/ > > > > > > On 6/17/07, Sudhir <sudhir.j-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > thanks a lot... will check them out... > > > > > > > > documented? even if they''re just the usual object expected messages? > > > > > > > > > > On Jun 17, 2:02 pm, "Fabian Lange" <Fabian.La...-S0/GAf8tV78@public.gmane.org> wrote: > > > > > Hello, > > > > > depending on what you want to analyze the new IE Debug Toolbar > > might > > > > > help > > > > > already: > > http://www.microsoft.com/downloads/details.aspx?FamilyID=E59C39 > > > > >64-672... BB3E-2D5E1DB91038&displaylang=en > > > > > > > > > > If you are really on JS only you should follow the guide > > > > > herehttp://blogs.msdn.com/ie/archive/2004/10/26/247912.aspx that > > at > > > > > least helps to some extend (but usability is quite low...) > > > > > > > > > > Another option is to google for the error. Most IE glitches are > > quite > > > > > well documented on the net > > > > > > > > > > .: Fabian > > > > > > > > > > -----Original Message----- > > > > > From: > > > > > > > > > > grbounce-_Pkz0AUAAAB9-VKt0-RY8LHUELm10l3Y> > fabian.lange=web...@googlegro > > > > >ups.c om > > > > > [mailto:grbounce-_Pkz0AUAAAB9-VKt0-RY8LHUELm10l3Y=fabian.lange=web.de@g > > > > >oogle groups.com] On Behalf Of Sudhir > > > > > Sent: Sonntag, 17. Juni 2007 10:43 > > > > > To: Ruby on Rails: Spinoffs > > > > > Subject: [Rails-spinoffs] JS debugger for IE > > > > > > > > > > hey, is there a good debugger for IE? i''ve tried searching for it, > > but > > > > > all i can find is the windows script editor :-/ and i''m not even > > sure > > > > > how well that works. firefox has superb stuff, but IE keeps > > throwing > > > > > up very vague errors with perfectly valid code :-/ > > > > -- > > Author: Prototype & Scriptaculous in Action, Ajax in Practice, Ajax in > > Action > > > > > > > > > > > -- > Ryan Gahl > Manager, Senior Software Engineer > Nth Penguin, LLC > http://www.nthpenguin.com > -- > Architect > WebWidgetry.com / MashupStudio.com > Future Home of the World''s First Complete Web Platform > -- > Inquire: 1-262-951-6727 > Blog: http://www.someElement.com <http://www.someelement.com/> > > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Ah yes. Well I guess it does involve just a bit of setup. But it''s not
really all that hard to get going. You can just think of this as a quick
"IE
test harness".
1. Create a new website. I just use File System, and just go ahead and
pick "ASP.NET Website". The language (Visual Basic or C#) is, of
course going to be unimportant if you''re just going to add a .html
file that
you intend to include some scripts in...
2. Add you .html file(s).
3. Copy your scripts somewhere within this new site structure on the
file system.
4. Include the scripts in your page... develop as normal.
5. To test:
1. In the "Solution Explorer", right-click on your .html file
and choose "Set as Start Page"
2. Open a script file that you want to debug, place your
breakpoint somewhere.
3. Hit F5 to launch the page.
4. Debug away.
Once you work through this a couple times it can just become part of your
project setup process. Yes... ''tis not ideal. But, it most definitely a
way
to get the job done!
On 6/20/07, Gareth Evans <agrath-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:>
> Ryan,
>
> How do you get the VWD debugger to kick in when you''re not doing
an
> ASP.Net website using cassani?
> I''ve had it kick in when i get a script error and i''m in
''debug mode'' for
> the website, (ie i can stop on breakpoints etc) but never seen it fire when
> ie throws a script error (say im running a .html file which is a sandbox
for
> some js development)
>
> Gareth
>
>
> On 6/21/07, Ryan Gahl
<ryan.gahl-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> > You can get VWD (Visual Web Developer) Express from MS for free, which
> > is basically VS pared down. That has excellent js debugging. Yes, I
use
> > firebug all the time, and love it. But yes, the js bebugging in VWD is
far
> > faster and more capable. I use firebug for FF dev, VWD for IE dev.
> >
> > On 6/19/07, Dave Crane
<dave-Sy7q136SasSXmMXjJBpWqg@public.gmane.org > wrote:
> > >
> > >
> > > Hi,
> > >
> > > These are nice (the bookmarklet idea in the third article
especially),
> > > but
> > > Firebug Lite only provides the logging console from Firebug, not
the
> > > javascript debugger. AFAIK, there really is nothing that comes
close
> > > to
> > > Firebug''s debugger for IE, not even if you cough up for
Visual Studio.
> > >
> > > Dave
> > >
> > > On Wednesday 20 June 2007 08:34, Nathaniel Brown wrote:
> > > > http://www.getfirebug.com/lite.html
> > > > http://www.phpied.com/firebug-console-for-ie/
> > > >
http://remysharp.com/2007/03/13/firebug-in-ie-for-any-web-site/
> > > >
> > > > On 6/17/07, Sudhir
<sudhir.j-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > > > > thanks a lot... will check them out...
> > > > >
> > > > > documented? even if they''re just the usual
object expected
> > > messages?
> > > > >
> > > > > On Jun 17, 2:02 pm, "Fabian Lange" <
Fabian.La...-S0/GAf8tV78@public.gmane.org> wrote:
> > > > > > Hello,
> > > > > > depending on what you want to analyze the new IE
Debug Toolbar
> > > might
> > > > > > help
> > > > > >
already:http://www.microsoft.com/downloads/details.aspx?FamilyID=E59C39
> > > > > >64-672... BB3E-2D5E1DB91038&displaylang=en
> > > > > >
> > > > > > If you are really on JS only you should follow the
guide
> > > > > >
herehttp://blogs.msdn.com/ie/archive/2004/10/26/247912.aspx that
> > > at
> > > > > > least helps to some extend (but usability is quite
low...)
> > > > > >
> > > > > > Another option is to google for the error. Most IE
glitches are
> > > quite
> > > > > > well documented on the net
> > > > > >
> > > > > > .: Fabian
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From:
> > > > > >
> > > > > > grbounce-_Pkz0AUAAAB9-VKt0-RY8LHUELm10l3Y> >
> fabian.lange=web...@googlegro
> > > > > >ups.c om
> > > > > >
[mailto:grbounce-_Pkz0AUAAAB9-VKt0-RY8LHUELm10l3Y=fabian.lange=web.de@g
> > > > > >oogle groups.com] On Behalf Of Sudhir
> > > > > > Sent: Sonntag, 17. Juni 2007 10:43
> > > > > > To: Ruby on Rails: Spinoffs
> > > > > > Subject: [Rails-spinoffs] JS debugger for IE
> > > > > >
> > > > > > hey, is there a good debugger for IE?
i''ve tried searching for
> > > it, but
> > > > > > all i can find is the windows script editor :-/
and i''m not even
> > > sure
> > > > > > how well that works. firefox has superb stuff, but
IE keeps
> > > throwing
> > > > > > up very vague errors with perfectly valid code :-/
> > >
> > > --
> > > Author: Prototype & Scriptaculous in Action, Ajax in
Practice, Ajax in
> > > Action
> > >
> > >
> > >
> > >
> >
> >
> > --
> > Ryan Gahl
> > Manager, Senior Software Engineer
> > Nth Penguin, LLC
> > http://www.nthpenguin.com
> > --
> > Architect
> > WebWidgetry.com / MashupStudio.com
> > Future Home of the World''s First Complete Web Platform
> > --
> > Inquire: 1-262-951-6727
> > Blog: http://www.someElement.com <http://www.someelement.com/>
> >
> >
> >
>
> >
>
--
Ryan Gahl
Manager, Senior Software Engineer
Nth Penguin, LLC
http://www.nthpenguin.com
--
Architect
WebWidgetry.com / MashupStudio.com
Future Home of the World''s First Complete Web Platform
--
Inquire: 1-262-951-6727
Blog: http://www.someElement.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
Oh... sorry, forgot 1 step: When you hit F5 to launch the page, it will ask you about adding a web.config file with debugging enabled - just say yes. On 6/20/07, Ryan Gahl <ryan.gahl-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > Ah yes. Well I guess it does involve just a bit of setup. But it''s not > really all that hard to get going. You can just think of this as a quick "IE > test harness". > > 1. Create a new website. I just use File System, and just go ahead > and pick " ASP.NET Website". The language (Visual Basic or C#) is, > of course going to be unimportant if you''re just going to add a .html file > that you intend to include some scripts in... > 2. Add you .html file(s). > 3. Copy your scripts somewhere within this new site structure on the > file system. > 4. Include the scripts in your page... develop as normal. > 5. To test: > 1. In the "Solution Explorer", right-click on your .html file > and choose "Set as Start Page" > 2. Open a script file that you want to debug, place your > breakpoint somewhere. > 3. Hit F5 to launch the page. > 4. Debug away. > > Once you work through this a couple times it can just become part of your > project setup process. Yes... ''tis not ideal. But, it most definitely a way > to get the job done! > > > On 6/20/07, Gareth Evans <agrath-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > Ryan, > > > > How do you get the VWD debugger to kick in when you''re not doing an > > ASP.Net website using cassani? > > I''ve had it kick in when i get a script error and i''m in ''debug mode'' > > for the website, (ie i can stop on breakpoints etc) but never seen it fire > > when ie throws a script error (say im running a .html file which is a > > sandbox for some js development) > > > > Gareth > > > > > > On 6/21/07, Ryan Gahl < ryan.gahl-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > > You can get VWD (Visual Web Developer) Express from MS for free, which > > > is basically VS pared down. That has excellent js debugging. Yes, I use > > > firebug all the time, and love it. But yes, the js bebugging in VWD is far > > > faster and more capable. I use firebug for FF dev, VWD for IE dev. > > > > > > On 6/19/07, Dave Crane <dave-Sy7q136SasSXmMXjJBpWqg@public.gmane.org > wrote: > > > > > > > > > > > > Hi, > > > > > > > > These are nice (the bookmarklet idea in the third article > > > > especially), but > > > > Firebug Lite only provides the logging console from Firebug, not the > > > > > > > > javascript debugger. AFAIK, there really is nothing that comes close > > > > to > > > > Firebug''s debugger for IE, not even if you cough up for Visual > > > > Studio. > > > > > > > > Dave > > > > > > > > On Wednesday 20 June 2007 08:34, Nathaniel Brown wrote: > > > > > http://www.getfirebug.com/lite.html > > > > > http://www.phpied.com/firebug-console-for-ie/ > > > > > http://remysharp.com/2007/03/13/firebug-in-ie-for-any-web-site/ > > > > > > > > > > On 6/17/07, Sudhir <sudhir.j-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > > > thanks a lot... will check them out... > > > > > > > > > > > > documented? even if they''re just the usual object expected > > > > messages? > > > > > > > > > > > > On Jun 17, 2:02 pm, "Fabian Lange" < Fabian.La...-S0/GAf8tV78@public.gmane.org> wrote: > > > > > > > Hello, > > > > > > > depending on what you want to analyze the new IE Debug Toolbar > > > > might > > > > > > > help > > > > > > > already:http://www.microsoft.com/downloads/details.aspx?FamilyID=E59C39 > > > > > > >64-672... BB3E-2D5E1DB91038&displaylang=en > > > > > > > > > > > > > > If you are really on JS only you should follow the guide > > > > > > > herehttp://blogs.msdn.com/ie/archive/2004/10/26/247912.aspx > > > > that at > > > > > > > least helps to some extend (but usability is quite low...) > > > > > > > > > > > > > > Another option is to google for the error. Most IE glitches > > > > are quite > > > > > > > well documented on the net > > > > > > > > > > > > > > .: Fabian > > > > > > > > > > > > > > -----Original Message----- > > > > > > > From: > > > > > > > > > > > > > > grbounce-_Pkz0AUAAAB9-VKt0-RY8LHUELm10l3Y> > > > fabian.lange=web...@googlegro > > > > > > >ups.c om > > > > > > > [mailto:grbounce-_Pkz0AUAAAB9-VKt0-RY8LHUELm10l3Y=fabian.lange=web.de@g > > > > > > >oogle groups.com] On Behalf Of Sudhir > > > > > > > Sent: Sonntag, 17. Juni 2007 10:43 > > > > > > > To: Ruby on Rails: Spinoffs > > > > > > > Subject: [Rails-spinoffs] JS debugger for IE > > > > > > > > > > > > > > hey, is there a good debugger for IE? i''ve tried searching for > > > > it, but > > > > > > > all i can find is the windows script editor :-/ and i''m not > > > > even sure > > > > > > > how well that works. firefox has superb stuff, but IE keeps > > > > throwing > > > > > > > up very vague errors with perfectly valid code :-/ > > > > > > > > -- > > > > Author: Prototype & Scriptaculous in Action, Ajax in Practice, Ajax > > > > in Action > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Ryan Gahl > > > Manager, Senior Software Engineer > > > Nth Penguin, LLC > > > http://www.nthpenguin.com > > > -- > > > Architect > > > WebWidgetry.com / MashupStudio.com > > > Future Home of the World''s First Complete Web Platform > > > -- > > > Inquire: 1-262-951-6727 > > > Blog: http://www.someElement.com <http://www.someelement.com/> > > > > > > > > > > > > > > > > > > > > -- > Ryan Gahl > Manager, Senior Software Engineer > Nth Penguin, LLC > http://www.nthpenguin.com > -- > Architect > WebWidgetry.com / MashupStudio.com > Future Home of the World''s First Complete Web Platform > -- > Inquire: 1-262-951-6727 > Blog: http://www.someElement.com >-- Ryan Gahl Manager, Senior Software Engineer Nth Penguin, LLC http://www.nthpenguin.com -- Architect WebWidgetry.com / MashupStudio.com Future Home of the World''s First Complete Web Platform -- Inquire: 1-262-951-6727 Blog: http://www.someElement.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Very real concerns, Dave. Yep, I code js the same way, and use anonymous
functions all over the place. There are some places where you''re right,
you
need a debug anchor to make a deep function line breakable. The standard way
of defining method, as you describe, though works fine in VWD. So yes,
I''ve
learned to live with the fact that if I want to step through some functions,
I need to place a debug anchor method call at the beginning...
For example:
test = Class.create();
test.prototype = {
initialize: function() {
//lines in here are breakpoint enabled
},
test: function() {
//same with this function
},
test2: function() {
var someArray = [1,2,3,4,5];
someArray.each(function(num) {
//trying to place a breakpoint in here results in the script
breaking no within the anonymous function, but at the point the .each()
method is called
});
}
}
So, the way to be able to step through those types of functions is to have
some generic empty method at a higher level (global is fine), place a
breakpoint within it, then call that function from within the anonymous
function you want to step through...
function AnonymousDebug() {
//place breakpoint on this line
}
...within test2() from the example above...
someArray.each(function(num) {
AnonymousDebug();
//when it breaks within that anchor function, you can then hit F11
to step into this function
});
So, as mentioned, ''tis not ideal, but you can workaround things. As I
understand, the script debugging facilities shipping with the next version
("Orcas") handles anonymous debugging much better.
The question was, "what''s the best tool available for free to
debug js in
IE".... VWD is it, and this is how... :-)
Oh, also, while debugging, in VWD you can go to "Debug > Windows >
Script
Explorer" to see the list of currently loaded script, including
eval''ed
code, which you can use to place breakpoints in and step through, which is
something firebug doesn''t let you do. So, right now, it''s a
trade off for
sure.
On 6/20/07, Dave Crane <dave-Sy7q136SasSXmMXjJBpWqg@public.gmane.org>
wrote:>
>
> Hi Ryan,
>
> Good point - I''ve seen the express vis studio editions,
didn''t make the
> connection. It''s a pretty big download/install for a debugger, but
hard
> disks
> and bandwidth are cheap these days, I guess!
>
> I''m currently using the Script Editor that comes with FrontPage
2003 (same
> thing that ships with VS 2003, I think? I hasten to add that I
don''t use
> Front Page for anything else, it''s just the cheapest route to
getting the
> script editor that I knew of!).
>
> Anyway, the one thing that really limits script editor''s
usefulness to me
> (and
> the freebie debugger is the same in this respect) is that the
> breakpoint-setter doesn''t understand inline function definitions,
e.g.
>
> 01 function blah(){
> 02 new Ajax.Request(
> 03 myURL,
> 04 { method: "POST",
> 05 onComplete:function(xhr){
> 06 var responseObj=Object.toJSON(xher.responseText);
> 07 doSomething(responseObj.this);
> 08 doSomethingElse(responseObj.that);
> 09 }
> 10 }
> 11 );
> 12 }
>
> stopping me from setting breakpoints on lines 6-8 interactively, which, in
> an
> Ajax app, is usually where a lot of the interesting stuff is going on.
> Worse,
> when I define a JS object type using Class.create() and the
> MyObjectType.prototype={ } approach, every method of the object is an
> inline
> function declaration, hence inaccessible to the debugger''s
breakpoint
> mechanism. The whole P&S coding style is geared around inline
functions,
> and
> not for trivial, stylistic reasons either. That functional-style
> programming
> approach has a very natural fit to JS as a language, and I''d be
loath to
> give
> it up these days.
>
> I can add a "debugger;" statement to my code within lines 6-8 and
reload
> the
> app, but that''s kind of tedious and defeats the immediacy of the
> interactive
> debugger. I could also stop defining functions inline, and pass references
> to
> top-level functions, but that would make my code look like death warmed
> up.
>
> OK, this is starting to sound like a rant - I''m not venting my
spleen at
> you,
> Ryan. You''ve got the VWD installed already, and say you like it.
Does the
> VWD debugger understand inline function declarations in the way
I''ve
> described (a basic prerequisite for being ''capable'' IMO)?
If so, I''ll
> happily
> burden my machine with it''s 300MB presence and abstain from saying
rude
> things about MS tools for, ooh, a whole day at least.
>
> TIA
>
> Dave Crane
>
> On Wednesday 20 June 2007 15:02, Ryan Gahl wrote:
> > You can get VWD (Visual Web Developer) Express from MS for free, which
> is
> > basically VS pared down. That has excellent js debugging. Yes, I use
> > firebug all the time, and love it. But yes, the js bebugging in VWD is
> far
> > faster and more capable. I use firebug for FF dev, VWD for IE dev.
> >
> --
> Author: Prototype & Scriptaculous in Action, Ajax in Practice, Ajax in
> Action
>
> >
>
--
Ryan Gahl
Manager, Senior Software Engineer
Nth Penguin, LLC
http://www.nthpenguin.com
--
Architect
WebWidgetry.com / MashupStudio.com
Future Home of the World''s First Complete Web Platform
--
Inquire: 1-262-951-6727
Blog: http://www.someElement.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
Yea, sure, that can end up being pretty convoluted. I just use it at the point I''ve narrowed an issue down to a particular area. I add in the anon function call, do the debugging, and delete it when I''m done. On 6/20/07, Dave Crane <dave-Sy7q136SasSXmMXjJBpWqg@public.gmane.org> wrote:> > > Hi Ryan, > > Oh well, that''s a shame, I was hoping to be proven wrong on this one :) > > I like the AnonymousDebug() function - lets you add the breakpoints > without > having to add debugger; statements into the code. But in a complex script, > wouldn''t you need several of these to avoid the breakpoint getting > triggered > whenever _anything_ happens, if you have lots of calls to it peppeed > through > the code. And if you need to uncomment the calls to the anon debug fn, > you''re > back to writing "debugger;" statements. > > I''ll give it a try anyway, and see what it feels like in practice. > > Cheers, > > Dave > > On Thursday 21 June 2007 15:37, Ryan Gahl wrote: > > Very real concerns, Dave. Yep, I code js the same way, and use anonymous > > functions all over the place. There are some places where you''re right, > you > > need a debug anchor to make a deep function line breakable. The standard > > way of defining method, as you describe, though works fine in VWD. So > yes, > > I''ve learned to live with the fact that if I want to step through some > > functions, I need to place a debug anchor method call at the > beginning... > > > > For example: > > > > test = Class.create(); > > test.prototype = { > > initialize: function() { > > //lines in here are breakpoint enabled > > }, > > > > test: function() { > > //same with this function > > }, > > > > test2: function() { > > var someArray = [1,2,3,4,5]; > > someArray.each(function(num) { > > //trying to place a breakpoint in here results in the script > > breaking no within the anonymous function, but at the point the .each() > > method is called > > }); > > } > > } > > > > > > So, the way to be able to step through those types of functions is to > have > > some generic empty method at a higher level (global is fine), place a > > breakpoint within it, then call that function from within the anonymous > > function you want to step through... > > > > function AnonymousDebug() { > > //place breakpoint on this line > > } > > > > ...within test2() from the example above... > > someArray.each(function(num) { > > AnonymousDebug(); > > //when it breaks within that anchor function, you can then hit > F11 > > to step into this function > > }); > > > > > > So, as mentioned, ''tis not ideal, but you can workaround things. As I > > understand, the script debugging facilities shipping with the next > version > > ("Orcas") handles anonymous debugging much better. > > > > The question was, "what''s the best tool available for free to debug js > in > > IE".... VWD is it, and this is how... :-) > > > > Oh, also, while debugging, in VWD you can go to "Debug > Windows > > Script > > Explorer" to see the list of currently loaded script, including eval''ed > > code, which you can use to place breakpoints in and step through, which > is > > something firebug doesn''t let you do. So, right now, it''s a trade off > for > > sure. > > > > On 6/20/07, Dave Crane <dave-Sy7q136SasSXmMXjJBpWqg@public.gmane.org> wrote: > > > Hi Ryan, > > > > > > Good point - I''ve seen the express vis studio editions, didn''t make > the > > > connection. It''s a pretty big download/install for a debugger, but > hard > > > disks > > > and bandwidth are cheap these days, I guess! > > > > > > I''m currently using the Script Editor that comes with FrontPage 2003 > > > (same thing that ships with VS 2003, I think? I hasten to add that I > > > don''t use Front Page for anything else, it''s just the cheapest route > to > > > getting the script editor that I knew of!). > > > > > > Anyway, the one thing that really limits script editor''s usefulness to > me > > > (and > > > the freebie debugger is the same in this respect) is that the > > > breakpoint-setter doesn''t understand inline function definitions, e.g. > > > > > > 01 function blah(){ > > > 02 new Ajax.Request( > > > 03 myURL, > > > 04 { method: "POST", > > > 05 onComplete:function(xhr){ > > > 06 var responseObj=Object.toJSON(xher.responseText); > > > 07 doSomething(responseObj.this); > > > 08 doSomethingElse(responseObj.that); > > > 09 } > > > 10 } > > > 11 ); > > > 12 } > > > > > > stopping me from setting breakpoints on lines 6-8 interactively, > which, > > > in an > > > Ajax app, is usually where a lot of the interesting stuff is going on. > > > Worse, > > > when I define a JS object type using Class.create() and the > > > MyObjectType.prototype={ } approach, every method of the object is an > > > inline > > > function declaration, hence inaccessible to the debugger''s breakpoint > > > mechanism. The whole P&S coding style is geared around inline > functions, > > > and > > > not for trivial, stylistic reasons either. That functional-style > > > programming > > > approach has a very natural fit to JS as a language, and I''d be loath > to > > > give > > > it up these days. > > > > > > I can add a "debugger;" statement to my code within lines 6-8 and > reload > > > the > > > app, but that''s kind of tedious and defeats the immediacy of the > > > interactive > > > debugger. I could also stop defining functions inline, and pass > > > references to > > > top-level functions, but that would make my code look like death > warmed > > > up. > > > > > > OK, this is starting to sound like a rant - I''m not venting my spleen > at > > > you, > > > Ryan. You''ve got the VWD installed already, and say you like it. Does > > > the VWD debugger understand inline function declarations in the way > I''ve > > > described (a basic prerequisite for being ''capable'' IMO)? If so, I''ll > > > happily > > > burden my machine with it''s 300MB presence and abstain from saying > rude > > > things about MS tools for, ooh, a whole day at least. > > > > > > TIA > > > > > > Dave Crane > > > > > > On Wednesday 20 June 2007 15:02, Ryan Gahl wrote: > > > > You can get VWD (Visual Web Developer) Express from MS for free, > which > > > > > > is > > > > > > > basically VS pared down. That has excellent js debugging. Yes, I use > > > > firebug all the time, and love it. But yes, the js bebugging in VWD > is > > > > > > far > > > > > > > faster and more capable. I use firebug for FF dev, VWD for IE dev. > > > > > > -- > > > Author: Prototype & Scriptaculous in Action, Ajax in Practice, Ajax in > > > Action > > -- > Author: Prototype & Scriptaculous in Action, Ajax in Practice, Ajax in > Action > > > >-- Ryan Gahl Manager, Senior Software Engineer Nth Penguin, LLC http://www.nthpenguin.com -- Architect WebWidgetry.com / MashupStudio.com Future Home of the World''s First Complete Web Platform -- Inquire: 1-262-951-6727 Blog: http://www.someElement.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---