Add jasmine-1.2.0

We're going to be writing unit tests for the features we're adding, and
we're using the Jasmine BDD framework.
Add the Jasmine test runners and helpers

These will be called directly from PhantomJS on the command line.
Move the vendor files inside of the test dir

These files are only needed to run the Jasmine test suite through
PhantomJS so keep them isolated within the same folder.
Simple tests for PlayerManager

These are in place to check that the test suite works as expected.
Use a local version of jQuery

The current examples for the media player suggest that they're
compatible with jQuery v1.6.0.
Use a jasmine TestRunner

This file is in place to help run the unit test suite.
Use a test helper to wrap the runner

In the cases where we're lazy, use this script to run the test suite.
Add youtube version of mediaplayer & tests

Creating a new version of the mediaplayer constructor already used in
the library.

The intention is to create an object with interface parity with
mediaplayer objects so that we can substitute our own youtube player
object without major refactorings.
Add jQuery UI

The lib requires it to be present for a lot of the logic and we need it
to exist to be able to consistently test the features we're intending to
improve.
Put YoutubePlayer on the window

It's already a global, so for the time being just assign it directly to
window so we can attach tests easier.
Initial integration tests for YoutubePlayer

These integration tests build out the DOM and initialise the jquery
player. At the moment it's just making sure our point of entry for
YoutubePlayer is as we expect.
Change toEqual to toBe

This makes the tests a little simpler to read, and more consistent.
Ensure Youtube Player is invoked correctly

Make sure

- the constructor isn't called with non-Youtube video URLs
- it is called with the correct parameters.
Capitalise to match other test descriptions
Add test for API script

Also correction of other syntax in other tests & begin API callback
test.
Get player dimensions from config

Assume config includes required properties.
Attach player to instance & ensure YT is reset
Clean up whitespace
Hook up control points between our player and Youtube

The short version: we're applying the interface that the mediaplayer()
object this library has uses against the Youtube iFrame API.

Most of these tests are highly evented which is why there are nested
waitsFor and runs blocks. These look dirty but they're the only way we
can satisfy an event has been handled over the network as part of the
request.

The biggest decision made here is to pass as much of the video controls
to the Youtube API. We shouldn't have to worry about much of what's
going on for the functionality to work.
Don't make Crockford cry

We shouldn't be using string literals to access an object's properties.