Firebug internals

  • Revision slug: Firebug_internals
  • Revision title: Firebug internals
  • Revision id: 108866
  • Created:
  • Creator: JohnJBarton1
  • Is current revision? No
  • Comment /* Major Components */

Revision Content

Get Firebug

Source Code

  1. Get Firebug; The source is included.
  2. Find the installed firebug in the Mozilla extensions directory, eg
C:\Documents and Settings\John J. Barton\Application Data\Mozilla\Firefox\Profiles\w5tmpjcs.test\extensions\firebug@software.joehewitt.com\
  1. Copy the directory to your workspace
  2. find firebug.jar in the chrome directory.
  3. rename it to firebug.zip.
  4. unzip it such that chrome directory contains the content of the jar,eg
  • chrome/content
  • chrome/icons
  • chrome/locale
  • chrome/skin

Rezip the files into a jar for testing.

Major Components

  • Panels - these are the tabs in the firebug UI
  • Modules - ?
  • lib aka FBL aka Firebug Library - common functions used in many panels
  • firebug-service - javascript - implemented XPCOM component, in firebug/components.
  • sourceCache - stores .htm, .js content read for source views
  • reps.js - representations usually used by multiple panels.
  • error.js - console observer for nsIScriptError and nsIConsoleMessage
  • XUL files - structure for the UI
  • css files - decorations
  • firebug.js
    • top.Firebug: version state
    • Base objects:
      • Firebug.Module, base for eg debugger
      • Firebug.Panel, interface for panels

Revision Source

<p><a class="external" href="http://getfirebug.com/">Get Firebug</a>
</p>
<h3 name="Source_Code"> Source Code </h3>
<ol><li> <a class="external" href="http://getfirebug.com/">Get Firebug</a>; The source is included.
</li><li> Find the installed firebug in the Mozilla extensions directory, eg
</li></ol>
<pre class="eval">C:\Documents and Settings\John J. Barton\Application Data\Mozilla\Firefox\Profiles\w5tmpjcs.test\extensions\firebug@software.joehewitt.com\
</pre>
<ol><li> Copy the directory to your workspace
</li><li> find firebug.jar in the chrome directory.
</li><li> rename it to firebug.zip.
</li><li> unzip it such that chrome directory contains the content of the jar,eg
</li></ol>
<ul><li>chrome/content
</li><li>chrome/icons
</li><li>chrome/locale
</li><li>chrome/skin
</li></ul>
<p>Rezip the files into a jar for testing.
</p>
<h3 name="Major_Components"> Major Components </h3>
<ul><li> Panels - these are the tabs in the firebug UI
</li><li> Modules - ?
</li><li> lib aka FBL aka Firebug Library - common functions used in many panels
</li><li> firebug-service - javascript - implemented XPCOM component, in firebug/components.
</li><li> sourceCache - stores .htm, .js content read for source views
</li><li> reps.js - representations usually used by multiple panels.
</li><li> error.js - console observer for nsIScriptError and nsIConsoleMessage
</li><li> XUL files - structure for the UI
</li><li> css files - decorations
</li><li> firebug.js 
<ul><li>top.Firebug: version state
</li><li>Base objects:
<ul><li>Firebug.Module, base for eg debugger
</li><li>Firebug.Panel, interface for panels
</li></ul>
</li></ul>
</li></ul>
Revert to this revision