Re: JS debugger on conceptual level

Yeah, remote (out-of-process) debugging in Mozilla is not trivial. I am not sure 
how you'd go about doing it - both Venkman and Firebug are in-process, which 
makes the process easier in a way. You could probably have part of your app 
install an add-on that deals with the Firefox interfaces for you, and control 
that add-on through whatever manner you wish (pipes/COM/screenscraping/local 
webserver/what-have-you).

~ Gijs

Dan wrote:
> Curious stuff.
> In IE world, I just attach to IE through a bunch of COM interfaces and get 
> an interface for a the running application from which I just set bpts and go 
> on.
> How does Firebug start debugging it?
> 
> Dan
> 
> "John J. Barton" <[email protected]> wrote in message 
> news:[email protected]...
>> Dan wrote:
>>> I am exploring a possilibity to add Firefox debugging into our Splinetech 
>>> JavaScript Debugger: www.remotedebugger.com
>>>
>>> Since it will only enrich mozilla if another debugger supports it, I 
>>> would like to learn more about how the FF debugger works conceptually. If 
>>> there is a diagram, that will be great.
>>> I obviously checked the firebug docs but I find it not clear.
>>> What are the essential classes and components that make the debugging 
>>> possible, and how do they interact with each other.
>> You might look at http://groups.google.com/group/webdebugprotocol?hl=en
>>
>> Are you only interested in JS debugging? Then all of the action in Firebug 
>> is in two files:
>> http://code.google.com/p/fbug/source/browse/branches/firebug1.5/components/firebug-service.js
>> http://code.google.com/p/fbug/source/browse/branches/firebug1.5/content/firebug/debugger.js
>>
>> Pretty standard stuff, except for the eval/event support.
>>
>> jjb 
> 
>