Incorporate a build step for sub-modules

[jessebeach]

For example, a test for #58 or HTML validation need external libraries.

[kevee]

How do we feel about using bower for this? I'm also looking at how we handle /dist per #57.

Are we going to need to dynamically load these (require.js?) per a test's dependencies, or will including on the page be the responsibility of the user?

[jessebeach]

Of course there's already a Grunt Task for it :)

https://github.com/yatskevich/grunt-bower-task

Sure, I'm open to exploring Bower. It's got Twitter behind it, so it's not some fly-by-night package manager.

[jessebeach]

I'd need to mess around with the components for a day to get a better understanding of how they'd interact, but in general, I'm never opposed to using existing tools rather than rolling custom code.

[kevee]

Agreed, the only question is whether we just build in external tools and tell users they need to include them for certain tests, or do we try to load them dynamically when quail needs them? We could have users do something like:

$('#stuff').quail({
  quailPath : '/path/to/quail'
});

Then we use that to see if a test has a dependency and if so just inject a script tag to a required library.

[kevee]

Added bower-dev branch to test building libs, works well, phantomjs is upset about something with the new version of qunit-composite for some reason, fixing now.

[kevee]

Merged in bower dev since tests passed and it's a nice standard.

[kevee]

Closing and updating progress issue on 2.1 release.