On Nov 24, 5:07 pm, John J Barton <[EMAIL PROTECTED]> wrote: > 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.
Hmm, I feared that this was going to be the case. Since my listeners will be 100% read-only I would hope there won't be any trouble with existing functionality. > For network and DOM we need more information, their are a lot of them. For network my extension will need to observe: 1. the http requests made by the browser when the document loads (html +css+script+images+objects etc) 2. any subsequent XHR calls. 3. the server responses to the above I'm only interested in the status and headers not the actual content itself. For DOM: I'm not 100% certain which events my extension will need to listen to but it will be a significant portion. Basically, anything that reflects user action on the page would have to be a part of it. Plus, any event that indicates modification of the DOM tree itself (for re-attaching the listeners) Again, all this is read-only, I don't anticipate doing anything to disrupt/modify the event flow. > > 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. I have a better understanding of the module and panel operations than I did at the beginning of the day so I'm encouraged :-) Tomorrow, I will do what you suggested and re-affirm things. Is there a FF option to redirect the console output to a file btw? Actually, having them both would be ideal. Thanks, Manoj --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
