Removed .DS_Store (god I hate those things).
Removed the QUnit directory. As much as it pains me to see my hard work gone, but let's face it, I decided to go with Mocha and that's that. Also added in some commented-out tests that are now failing, but that's because I don't have PhantomJS in place yet. It's kind of behavior testing... but kind of not.
Super tired. Tests. Stuff. CLeanup. Need to merge the test utils (I'm definitely naming that back to utils-test.js) with the main test runner. Great progress though.
I don't even know.
One of the tests is still failing, but everything else is cleaned up. Some of the tests are commented out right now: dispatchEvent() because I haven't done the async stuff yet, and all the seekTo stuff because it's a player behavior and without the PDK, an error gets thrown for every single event. I may want to consider not throwing an error and queueing up function calls instead.
Started writing the query module as well as the helpers to go along with it to help keep it clean (removeQueryParams(), isFeedURL(), isReleaseURL(), etc.).
Fixed the guid helper and started really building out the getVideo() method. Also changed _defaults to _defaultsConfig since it's more descriptive. I'd like to also add an array of properties that aren't overridable and figure out a way to handle that with underscore. Maybe just extend the _.defaults() method.
Fixed the isURL() method so that the regex supports www and query params.
More tests.
Wrote some more tests and filled out the methods to match them some more.
Fixing up the functions I so sorely need to work VERY reliably. Using TDD to get there. Kind of awesome, really.
Since we committed to Mocha, I just moved everything into the convetional 'test' folder since Mocha scrubs for ./test/*.js when you run mocha from the command line. Speaking of which, doing that causes all kinds of problems (no window object, nothing was getting pulled in since the dependencies need to be pulled in with require, etc). I need to clean that up by using PhantomJS I'm pretty sure, but that's the next step. Baby steppin'...
something
Site modal now being used.

I created the checks and htmlFragment (which based on Michelle's
example looks like it needs to be a jQuery element), and passed it to
the VideoAuth.Modal. That will change in the future, but for now this
is how we can leverage it.
The unit tests are split up into multiple files (and a reference to tests.js just in case). I've almost got these things running from the command line, but I'm hitting issues with dependencies on the window object. I need to learn more about mocking/stubbing, but I might be able to use PhantomJS too - not sure which is better.
Fixed the JSHint errors from the AuthModal stuff.
Version 0.4.0

The query module can be used for interacting with feeds to retrieve video objects.

The Dispatcher class got a new method, some debug statements were cleaned up, more tests were written, and most importantly the README has been updated to have some API documentation in it. Long way to go, but I'm going to make it a requirement when submitting a new module.

Signed-off-by: Brandon Aaskov <aaskov@gmail.com>
Fixed event dispatching (and a few other tidbits).

The event dispatching wasn't very stable. It's tested now and works a whole lot better… in that it works. Also added addScriptTag() to utils. I added callback responses to getVideo(), and I'm now checking for jQuery before assigning it (not that it matters, I think).

Signed-off-by: Brandon Aaskov <aaskov@gmail.com>
Fixed up the README.
Broke out the unit tests into their own modules - that tests.js file was getting too huge.