Firebug Architecture

From FirebugWiki

(Difference between revisions)
Jump to: navigation, search
(Resources)
(Unified Rendering)
 
(13 intermediate revisions not shown)
Line 2: Line 2:
== Resources ==
== Resources ==
-
* [https://getfirebug.com/wiki/index.php/Script_Panel_Refactoring Script Panel Refactoring]
+
* [[Script Panel Refactoring]]
-
* [[Remoting Architecture|Remoting Architecture]]
+
* [[Remoting Architecture]]
-
* [http://www.softwareishard.com/slides/firebug/LondonSep2012/FirebugArchitectureHighlights.pdf Firebug Architecture Highlights (pdf)]
+
* [[Data Providers & Viewers]]
-
* [[Data Providers|Data Providers]]
+
 
 +
== Internal Concepts And Components ==
 +
 
 +
Brief summary of internal concepts used in Firebug's framework.
 +
 
 +
TODO: create structure of internal concepts + patterns and link to individual pages that provide detailed explanation. Use [http://www.softwareishard.com/slides/firebug/LondonSep2012/FirebugArchitectureHighlights.pdf Firebug Architecture Highlights (pdf)] slides.
 +
 
 +
=== <code>Firebug</code> Object ===
 +
The <code>Firebug</code> object is the only global object and represents the roof object of the entire application. The main purpose of the object is to be used as a registry. For instance all ''Module'' and ''Panel'' objects are registered, so the frameworks knows where to send events to or what panels should be created.
 +
 
 +
Used patterns:
 +
* Singleton
 +
 
 +
=== Context ===
 +
A <code>context</code> object represents a document and is responsible for collecting (meta) data about the current page, on which Firebug is active. The <code>context</code> object is also responsible for creating instances of the registered ''Panel'' objects.
 +
 
 +
Related patterns:
 +
* Document
 +
* Factory
 +
 
 +
=== Panel ===
 +
A <code>panel</code> object is used to present information to the user. The displayed data is always related to the current page. A panel is accessing the current <code>context</code> object to render relevant data.
 +
 
 +
Related Patterns:
 +
* View
 +
* Presentation State
 +
 
 +
Read more about concepts used in the [[Script Panel Refactoring|Script Panel]].
 +
 
 +
=== Module ===
 +
(Services)
 +
 
 +
TODO
 +
 
 +
=== Tool ===
 +
(the same life cycle like a panel, but no UI)
 +
 
 +
TODO
 +
 
 +
=== Navigation & Selection ===
 +
TODO
 +
 
 +
=== Event Sources (Listener) ===
 +
TODO
 +
 
 +
=== Data Providers & Viewers ===
 +
Firebug uses the viewer-provider pattern to unify the way how UI widgets (viewers) access various data sources. The pattern supports synchronous as well as asynchronous data sources and allows to use a common API to access them.
 +
 
 +
Related patterns:
 +
* Provider
 +
* Viewer
 +
* Presentation State
 +
 
 +
Read a detailed explanation about [[Data Providers & Viewers]].
 +
 
 +
=== Unified Rendering ===
 +
(Domplate)
 +
 
 +
=== Electrolysis ===
 +
The purpose of this Firefox project is to run web content in a separate process from Firefox itself. This obviously has impact also on Firebug that needs IPC channels in order to access web content.
 +
 
 +
Read more about [[Electrolysis|related concepts]].
 +
 
 +
== Extensions ==
 +
Firebug offers also [[Firebug 1.10 Extension Architecture|APIs for extensions]].
 +
 
 +
[[Category:Firebug]]
 +
[[Category:Firebug Development]]

Latest revision as of 07:15, 17 December 2013

This page covers the architecture of Firebug (the Firefox extension), showing internal concepts and explaining how individual components interact when Firebug is running.

Contents

[edit] Resources

[edit] Internal Concepts And Components

Brief summary of internal concepts used in Firebug's framework.

TODO: create structure of internal concepts + patterns and link to individual pages that provide detailed explanation. Use Firebug Architecture Highlights (pdf) slides.

[edit] Firebug Object

The Firebug object is the only global object and represents the roof object of the entire application. The main purpose of the object is to be used as a registry. For instance all Module and Panel objects are registered, so the frameworks knows where to send events to or what panels should be created.

Used patterns:

  • Singleton

[edit] Context

A context object represents a document and is responsible for collecting (meta) data about the current page, on which Firebug is active. The context object is also responsible for creating instances of the registered Panel objects.

Related patterns:

  • Document
  • Factory

[edit] Panel

A panel object is used to present information to the user. The displayed data is always related to the current page. A panel is accessing the current context object to render relevant data.

Related Patterns:

  • View
  • Presentation State

Read more about concepts used in the Script Panel.

[edit] Module

(Services)

TODO

[edit] Tool

(the same life cycle like a panel, but no UI)

TODO

[edit] Navigation & Selection

TODO

[edit] Event Sources (Listener)

TODO

[edit] Data Providers & Viewers

Firebug uses the viewer-provider pattern to unify the way how UI widgets (viewers) access various data sources. The pattern supports synchronous as well as asynchronous data sources and allows to use a common API to access them.

Related patterns:

  • Provider
  • Viewer
  • Presentation State

Read a detailed explanation about Data Providers & Viewers.

[edit] Unified Rendering

(Domplate)

[edit] Electrolysis

The purpose of this Firefox project is to run web content in a separate process from Firefox itself. This obviously has impact also on Firebug that needs IPC channels in order to access web content.

Read more about related concepts.

[edit] Extensions

Firebug offers also APIs for extensions.

Personal tools