it's a tool. For testing
As it stands, Winston has two different installation options. From the base directory you run
./build <env>
Essentially, what this script does is collects the important files from lib, "compiles" them, and moves everything into bin.
-Regular: Only runs on local URL's. This is useful in that the injection script doesn't go into every other damn page in chrome.
-Expanded: The script is injected, and the tool is available in any webpage on chrome. This is useful while testing Winston's questionable robustness.
-Dev: Meant to be loaded as an unpacked extension from the bin directory.
Each of this is generated from a specific manifest file under lib/. To create your own type of installation, simply make your own manifest in lib with a unique name, and run ./build.sh. An installation directory named after your manifest will be created in /install, and the .crx will reflect your own speciall install .crx. Look at you....
The .crx is the actual install file.
To install, go to the install folder and open whatever type you want to install. Inside of that folder is a winston.crx and a winston.pem. Don't worry about the .pem (TODO: Tell people to worry about the keyfile).
With chrome's extension page open, drag the .crx file into it. Say yes to the permissions. You can trust me.
So after you've installed, there's this smug fucking squirrel in your extensions bar. If you're using an unpacked dir (dev), it's just a puzzle piece. When you're at a place where your integration test should start, click that shit.
At this point, the bar shows up wherever the options depict it (default bottom right).