Hmm... does it really matter?  It's a feature request, not a bug
report.

If you really must know, I am currently using 1.3.3.   And I've read
your latest blog post about the script panel performance (http://
blog.getfirebug.com/?p=105).  But the truth is that no matter how fast
you make the script panel with execution line marking, it's still
going to be slower than without.  And I just don't care about the
feature.  I already know which lines are executable.  I don't need a
visual reminder.

If it's the amount of work invovled, then here is a patch that a guy I
work with made which adds a config option that can be set to disable
it:

-------------------------------------------------
Patch for defaults/preferences/firebug.js:

>> >> cat firebug.patch
--- firebug.old.js      2009-02-19 11:21:36.000000000 -0600
+++ firebug.js  2009-02-27 16:08:01.000000000 -0600
@@ -92,6 +92,7 @@
 pref("extensions.firebug.DBG_FBS_FF_START", false); // firebug trace
from FF start(huge) /*...@explore*/
 pref("extensions.firebug.DBG_FBS_CREATION", false); // firebug script
creation           /*...@explore*/
 pref("extensions.firebug.DBG_FBS_BP", false);       // firebug
breakpoints               /*...@explore*/
+pref("extensions.firebug.DBG_HIGHLIGHT_EXECUTABLE", true);     //
firebug highlight executable code /*...@explore*/
 pref("extensions.firebug.DBG_FBS_SRCUNITS", false); // firebug script
creation           /*...@explore*/
 pref("extensions.firebug.DBG_FBS_ERRORS", false);   // firebug
errors                    /*...@explore*/
 pref("extensions.firebug.DBG_FBS_FINDDEBUGGER", false);   // firebug
findDebugger        /*...@explore*/


Patch for content/firebug/debugger.js:

>> >> cat debugger.patch
--- debugger.old.js     2009-02-19 11:21:36.000000000 -0600
+++ debugger.js 2009-02-27 16:09:12.000000000 -0600
@@ -1563,6 +1563,17 @@

     markExecutableLines: function(sourceBox)
     {
+        var prefs = Components.classes["@mozilla.org/preferences-
service;1"]
+                        .getService
(Components.interfaces.nsIPrefService);
+        prefs = prefs.getBranch("extensions.firebug.");
+
+        var value = prefs.getBoolPref("DBG_HIGHLIGHT_EXECUTABLE");
+
+        if (! value)
+        {
+            return;
+        }
+
         var sourceFile = sourceBox.repObject;
         var lineNo = sourceBox.firstViewableLine;
         while( lineNode = sourceBox.getLineNode(lineNo) )
-------------------------------------------------

On Feb 27, 4:05 pm, John J Barton <[email protected]> wrote:
> Which version of Firebug?
> jjb
>
> On Feb 27, 1:57 pm, Steve <[email protected]> wrote:
>
>
>
> > I don't know if this has been mentioned before, as I couldn't find
> > anything about it by searching, but could an option be added to enable/
> > disable the marking of executable lines?  I've taken to modifying the
> > plugin myself in order to disable to the functionality since it slows
> > down my debugging significantly.
>
> > Thanks- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
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