ios-webkit-debug-proxy description

Added description of how to install and use the ios-webkit-debug-proxy.
Updated cloning description

Tried to make it a bit clearer about what brew install does and simply installing the proxy manually.
Merge pull request #655 from snevesbarros/patch-1

ios-webkit-debug-proxy description
Merge pull request #656 from snevesbarros/master

Local Grid setup documentation
Updating Windows Instructions
Implementing setLocation for iOS
Merge pull request #652 from penguinho/master

Implementing setLocation for iOS
Use === 1 for isVisible check

Fix #653
Merge pull request #657 from bootstraponline/===

Use === 1 for isVisible check
fix isBundle regex
refactor and add more logging to instruments_client.js
update style guide
update uicatalog tests to work with new uicatalog app
Merge pull request #661 from jlipps/master

grab bag of fixes/updates
Fix fast reset race condition

adb shell am commands return immediately, not when they're finished. am
instrument will close the app once it completes. It's possible for instrument to
be running, the am start command is issued, then instrument finishes and closes
the app. Appium is now waiting for an activity that will never appear and the
tests fail.

The fix is to only start the app once reset has closed the app.

Fixes #662
Merge pull request #663 from bootstraponline/fix_reset_timing

Fix fast reset race condition
Added changes to notify websocket listeners of alert dialogs.

One thing to keep in mind: iOS and Android treat dialogs differently. iOS "system" dialogs can be triggered from the application under test as well as from external sources (the system). However, Android treats dialogs as any other window. So, to make this work, the bootstrap app looks for windows with the package name of "com.android.systemui". These are dialogs that the system has instantiated, but not the app.

So, for example, if we had the same application written on both platforms, and they both had a login screen, and you click on the login button without putting in a username. On iOS, you would be notified if they used a standard system dialog, and you would not be notified on Android. However, if the system put up a low battery dialog, it would be detected on both systems.

So... The main reason for implementing this is to stop failing tests from unintentional dialogs appearing during an overnight test.

Updated call signiture to instruments.
Merge pull request #624 from mutualmobile/websocket_notifications_for_alerts

Added changes to notify websocket listeners of alert dialogs.
make android manifest xml src part of build/
make the change simpler, just include the file in npm