On Nov 24, 11:48 am, Manoj <[EMAIL PROTECTED]> wrote:
> I followed the excellent introduction to getting started with firebug
> extensions (Part I - IV) written by Honza. As you may recall my
> interest is to develop a utility which collates the network,
> javascript and DOM event activity for a page and ultimately produce a
> usable display.
>
> To achieve this, i'm trying to figure out how my extension will be
> able to listen in on the following:
>
> 1. JavaScript function calls/returns
> 2. Network requests/responses
> 3. DOM events
Generally you'll listen to Firefox for these, just like Firebug does.
Firebug events are at a higher level, more like "debugger stopped"
than "function call".
The function call and return will require addition to the firebug-
service (jsd interface). Its not difficult as long as we can figure
out how to avoid colliding with single stepping.
For network and DOM we need more information, their are a lot of them.
>
> Is there a writeup on *how* such existing Firebug functionality can be
> re-used?
> Any pointers would be appreciated.
>
> In the meantime, I'm overriding the module and panel methods one by
> one in an effort to understand when they are being called and the most
> appropriate way I can attach / detach my listeners into Firebug.
A good place to start is the Firebug Tracing Console, (or Chromebug if
you are very brave).
Set Options DISPATCH to or PANELS one at a time and operate the UI.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Firebug" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/firebug?hl=en
-~----------~----~----~----~------~----~------~--~---
