diff options
Diffstat (limited to 'devtools/server/docs/actor-registration.md')
-rw-r--r-- | devtools/server/docs/actor-registration.md | 41 |
1 files changed, 41 insertions, 0 deletions
diff --git a/devtools/server/docs/actor-registration.md b/devtools/server/docs/actor-registration.md new file mode 100644 index 000000000..8d79d9372 --- /dev/null +++ b/devtools/server/docs/actor-registration.md @@ -0,0 +1,41 @@ +# How to register an actor + +## Tab actors vs. global actors + +Tab actors are the most common types of actors. That's the type of actors you will most probably be adding. + +Tab actors target a document, this could be a tab in Firefox, an app on B2G or a remote document in Firefox for Android/Safari/Chrome for Android (via Valence). + +Global actors however are for the rest, for things not related to any particular document but instead for things global to the whole Firefox/B2G/Chrome/Safari intance the toolbox is connected to (e.g. the preference actor). + +## The DebuggerServer.registerModule function + +To register a tab actor: + +``` +DebuggerServer.registerModule("devtools/server/actors/webconsole", { + prefix: "console", + constructor: "WebConsoleActor", + type: { tab: true } +}); +``` + +To register a global actor: + +``` +DebuggerServer.registerModule("devtools/server/actors/addons", { + prefix: "addons", + constructor: "AddonsActor", + type: { global: true } +}); +``` + +If you are adding a new built-in devtools actor, you should be registering it using `DebuggerServer.registerModule` in `addBrowserActors` or `addTabActors` in `/devtools/server/main.js`. + +If you are adding a new actor from an add-on, you should call `DebuggerServer.registerModule` directly from your add-on code. + +## A note about lazy registration + +The `DebuggerServer` loads and creates all of the actors lazily to keep the initial memory usage down (which is extremely important on lower end devices). + +It becomes especially important when debugging apps on b2g or pages with e10s when there are more than one process, because that's when we need to spawn a `DebuggerServer` per process (it may not be immediately obvious that the server in the main process is mostly only here for piping messages to the actors in the child process). |