Feature/bower

## Package Manage Rosy with [Bower](http://twitter.github.com/bower/)

### Requirements

* `npm install bower -g`

### Quick Start : Example Project

For our test case, you can download and install the Rosy [example project](https://github.com/rosy-components/example).

 * `mkdir example && cd example`
 * `bower install git@github.com:rosy-components/example.git`
 * `mv components/example/html/index.html index.html` // move a couple example html files 
 * `mv components/example/html/about.html about.html`
 * `http-server`
 * Point brower to [http://localhost:8080](http://localhost:8080)

### How to run [OxBlood tests](https://github.com/rosy-components/rosy-oxblood)
 
 Lets demo the Oxblood test-suite on `rosy`.
 
 * Install OxBlood depencencies
  * `brew install phantomjs` // more info on [Oxblood](https://github.com/rosy-components/rosy-oxblood)
  * `npm install http-server -g`
 * Install OxBlood tests locally into your code-base
  * `cd example/components/rosy` OR `cd example/components/[some-rosy-component]`
  * `npm install` // installs the OxBlood test-suite into the library you're testing
  * `npm test` // runs tests in node PhantomJS browser. 
  * OR `http-server` and go to [localhost:8080/node_modules/rosy-oxblood/runner.html](http://localhost:8080/node_modules/rosy-oxblood/runner.html) // run tests in your browser
 
### Details
 
 * If all you want is Rosy, just do `bower install git@github.com:ff0000/rosy.git#1.0.0-bower`.
 * List of rosy-components available at the [rosy-components group](https://github.com/rosy-components).
 * Hopefully, this makes using and contributing rosy-components easier. You can store tests and examples in your component repo.
 * Customizing and running `OxBlood` tests is easier.

### Roadmap

 * Once accepted, we'll register Rosy with Bower so you can just `bower install rosy`
 * Working on an OxBlood `readme` to help setup and run custom OxBlood tests on your projects and libs.
 * Travis and Bunyip tests aren't working with the new package organization - will work on correcting this.