blob42
/
angularjs-batarang
Archived
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
This repo is archived. You can view files and clone it, but cannot push or open issues/pull-requests.
master
test-unit-sauce
v0.3.0
v0.3.1
v0.3.2
v0.4.0
v0.4.1
v0.4.2
v0.4.3
v0.5.0
v0.6.0
v0.6.1
v0.7.0
v0.7.1
v0.7.2
v0.7.3
v0.7.4
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'cd2a9e495d'
${ noResults }
angularjs-batarang/ARCHITECTURE.md

945 B
Raw Blame History Unescape Escape

Batarang Architecture

This document describes the different parts of Batarang and how they interact with the aim to be useful for anyone that wants to help improve Batarang.

Parts

Devtools Elements pane

Devtools Pane

Dispays stuff

Instrumentation

Hooks into the app to give you stats and access to the models.

Background Page

  • Lets us communicate between app and devtools pane
  • Stores state

Bootstrap

How does Batarang start? When a tab is opened in Chrome:

  1. Chrome reads the manifest.json – specifically the content_scripts field.
  2. content script – conent-scripts/inject.js
  • checks for the presense of an __ngDebug cookie
  • embeds <script> into the app's <head>
    • adds a mutation listener
  1. proxy elt
  2. app context patches angular
  3. emits events to content script
  4. content script sends messages to the backgroung page
  5. backgroung page emits events to the devtools pane