I looked at the XUL tree and seems like it would be appropriate for
displaying this type of information. I plan to spend some more time to
understand Firebug's existing UI to see if I can get something going.
Basically, I'll be working along creating a separate panel which will
have a call tree display akin to the current DOM or HTML panels.

Regards,
Manoj

On Nov 17, 5:44 pm, John J Barton <[EMAIL PROTECTED]> wrote:
> Something like this is feasible, you probably know the potential
> problems. The two big ones are UI (as Honza suggested by asking) and
> performance. The interesting cases for this kind of feature are large
> complex systems which generate lots of call stack information.   I
> think a highly interactive tool would be more promising and fun,
> versus batch processing record/playback.
>
> You might have to try a couple of approaches. Also the same technology
> could be applied to get code coverage as well.
>
> jjb
>
> On Nov 14, 10:43 pm, Manoj <[EMAIL PROTECTED]> wrote:
>
> > I was wondering if it would be possible to enhance FB to capture and
> > display runtime call graphs along with event information and XHR
> > communication. The use for such an option would be to rapidly
> > understand web application logic (especially when dealing with 3rd
> > party applications) and be able to focus on the relevant script.
>
> > I've installed the trace enabled version and will be playing with it
> > some more to gain a better understanding of the internals (FWIW, I'm a
> > newbie to FF extension development, XUL etc.)  I'm willing to invest
> > my time into this and should be able to convince my employer as well.
> > Would appreciate if someone more qualified can comment on the
> > feasibility of such a project and/or point me in the right direction.
>
> > 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to