On Nov 24, 5:36 pm, Manoj <[EMAIL PROTECTED]> wrote:
> On Nov 24, 5:07 pm, John J Barton <[EMAIL PROTECTED]> wrote:
...
>
> > 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.
The jsd layer only allows one listener, so read-only or not, we need
to deal with it.
>
...
> > 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.
Firebug console? Firebug tracing console? OS console? Both of which?
I guess you mean "window.dump()"? You can use normal OS redirection on
the command line or open a file an write into it.
You can write to the FBTrace console and/or window.dump() from your
code.
jjb
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
