I've been working on a FF extension for quite a while now and have been relying on the FF 5, Firebug 1.72 + Chromebug 1.72 environment to have a robust debug environment for my extension. I of course understand these are old versions that are bound to break at some point. I have read the XULRunner tips you link to below and I'm sure I 100% understand what is possible with the current set of releases.
FBTrace seems to be more of a console output - which though helpful, is not entirely what I'm looking for. Do you know if there is a combination of tools such that I could debug my extension (step-through javascript code, examine the Chrome DOM, HTML, etc) with the current Firebug in the way that ChromeBug used to do? I apologize if there is an answer I should know already - I'm just having trouble getting a clear picture. I haven't yet installed the latest Firebug (maybe it does all this natively? ) for fear of breaking my brittle dev environment : ) Thanks again for an awesome tool. Best, Ben On Wednesday, May 9, 2012 12:48:37 AM UTC-4, Sebo wrote: > > Note, as it was stated in the other thread Chromebug is not working with > newer versions of Firebug than 1.7. So you will need to use > FBTrace<http://getfirebug.com/wiki/index.php/FBTrace>instead. Also there is > also no maintenance for older versions of Firebug > than 1.9 <https://addons.mozilla.org/de/firefox/addon/firebug/> anymore. > Currently we're working on Firebug 1.10<https://github.com/firebug/firebug> > . > > The XULRunner tips <https://developer.mozilla.org/en/XULRunner_tips> will > help you to enable extensions support. If you decide to stay with Firebug > 1.7 (which I do not recommend), you will need to adjust the toolkit > maxVersion to 5.* inside the > install.rdf<http://code.google.com/p/fbug/source/browse/branches/firebug1.7/install.rdf>first. > Though I never tried that. So there's no guarantee that it works. > If you can't get Firebug to work, you may at least be able to get DOM > Inspector > running<https://developer.mozilla.org/en/XULRunner_tips#DOM_Inspector> > . > > Sebastian > > On Tuesday, May 8, 2012 4:20:48 PM UTC+2, kja wrote: >> >> I am developing an XULRunner application which is strictly a client >> browser application, (necessary to meet a client contract >> requirement). Success requires me to get Chromebug/Firebug and/or >> FBTrace, or some other debug environment operational. I am flexible >> with respect to which XULRunner I use (5.0 or greater). I am currently >> using 5.0. >> >> I have seen some indication that FF5.0 is compatible with FB 1.7 / CB >> 1.7 (see ==> >> >> http://groups.google.com/group/firebug/browse_thread/thread/c7b7d1964ac5c635/26016744e712538c?lnk=gst&q=firebug+chromebug#26016744e712538c >> >> ). >> >> I am willing to expend the time to confirm a working environment, >> however I would prefer to start my efforts with a last-known working >> environment, if one such environment can be confirmed and if a single >> page of installation theory can be pointed to. >> >> Is anyone currently or recently using CB/FB with XULRunner? If so, >> what versions? > > -- 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 https://groups.google.com/forum/#!forum/firebug
