Remoting Prototype

From FirebugWiki

This page is intended to provide detailed instructions about how to use remote capabilities in Firebug.

Contents 1 Resources 2 Prototype 2.1 Setup 2.1.1 Server 2.1.2 Client 2.2 FBTrace 2.3 Implementation 3 Working Scenarios

[edit] Resources

• Firebug 1.7 BTI
• Script Panel Refactoring

[edit] Prototype

The current development happens on the jsd2 branch.

[edit] Setup

See how to setup your environment to successfully connect Firebug to remote browser instance. Note that you need to install Firebug on both sides, client and server.

Following preferences need to be set (use about:config)

[edit] Server

• devtools.debugger.remote-enabled - must be set to true
• extensions.firebug.serverMode - must be set to true
• devtools.debugger.force-local - set to false if you want to connect to browser instance on another machine

[edit] Client

• extensions.firebug.serverHost - name of the remote host (localhost by default)
• extensions.firebug.serverPort - remote port (5999 by default)

In order to make a connection start both browser instances (use two Firefox profiles if testing on one machine). The client side should automatically try to connect the server according to the settings. See the Connecting... button in the main Firebug toolbar.

[edit] FBTrace

In order to see/filter logs on the server and client you should use following options in the FBTrace console.

• CONNECTION - Use this option to see packet communication. Every log is also associated with the packet so, you can simply explore its structure.

• BTI - See various logs related to BTI architecture such as registering various BTI listeners.

[edit] Implementation

Rough summary of steps to implement a remotable Firebug prototype (starting with the Script and Net Panel).

• Create a simple server side to connect to
• Implement basic connection object
• Provide simple UI to allow the user to connect the server
• Implement custom actors on the server side
• Implement new Script panel supporting remotable architecture
• Implement Script panel proxy on top of the connection object
• Move UI pieces from the old (JSD1 based) Script panel step by step into the new (JSD2 based) Script panel.
• Connect existing built-in script-debugger actors

[edit] Working Scenarios

Some use-cases are already working.

• Stepping