blob42
/
angularjs-batarang
Archived
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

docs: improve arch doc

Browse Source
test-unit-sauce
Brian Ford 10 years ago
parent 514eddcda9
commit 253337e55f
1 changed files with 12 additions and 9 deletions
Show Stats Download Patch File Download Diff File

21
ARCHITECTURE.md
Unescape Escape View File

@ -1,17 +1,19 @@
# Batarang Architecture # Batarang Architecture
This document describes the different parts of Batarang and how they interact. This document describes the different parts of Batarang and how they interact
This is intended for anyone that wants to contribute to or improve Batarang. with the aim to be useful for anyone that wants to help improve Batarang.
## Parts ## Parts
### Chrome Devtools Pane ### Devtools Elements pane
### Devtools Pane
Dispays stuff Dispays stuff
### Instrumentation ### Instrumentation
Hooks into the app to give you stats and access to the models Hooks into the app to give you stats and access to the models.
### Background Page ### Background Page
- Lets us communicate between app and devtools pane - Lets us communicate between app and devtools pane
@ -20,12 +22,13 @@ Hooks into the app to give you stats and access to the models
## Bootstrap ## Bootstrap
How does Batarang start? How does Batarang start? When a tab is opened in Chrome:
1. `manifest.json` – ... 1. Chrome reads the `manifest.json` – specifically the `content_scripts` field.
2. content script 2. content script – `conent-scripts/inject.js`
- crazy bootstrap * checks for the presense of an `__ngDebug` cookie
3. embeds `<script>` into the app's `<head>` * embeds `<script>` into the app's `<head>`
- adds a mutation listener
4. proxy elt 4. proxy elt
5. app context patches angular 5. app context patches angular
6. emits events to content script 6. emits events to content script