Firebug Object is the only global object and represents a roof object in 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 or what panels should be created.

+

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:

Used patterns:

Line 19:

Line 19:

=== Context ===

=== 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.

+

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:

Related patterns:

Line 26:

Line 26:

=== Panel ===

=== Panel ===

-

A panel object is used to present information to the user. Displayed data are always related to the current page. A panel is accessing the current ''Context'' object to render relevant data.

+

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:

Related Patterns:

Line 32:

Line 32:

* Presentation State

* Presentation State

-

Read more about concepts used in the [https://getfirebug.com/wiki/index.php/Script_Panel_Refactoring Script Panel]

+

Read more about concepts used in the [[Script Panel Refactoring|Script Panel]].

=== Module ===

=== Module ===

(Services)

(Services)

+

+

TODO

+

+

=== Tool ===

+

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

+

+

TODO

=== Navigation & Selection ===

=== Navigation & Selection ===

+

TODO

=== Event Sources (Listener) ===

=== Event Sources (Listener) ===

+

TODO

=== Data Providers & Viewers ===

=== Data Providers & Viewers ===

-

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

+

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:

Related patterns:

Line 49:

Line 58:

* Presentation State

* Presentation State

-

Read detailed explanation about [[Data Providers & Viewers]].

+

Read a detailed explanation about [[Data Providers & Viewers]].

=== Unified Rendering ===

=== Unified Rendering ===

(Domplate)

(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.

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.

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.

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.