Manage client-side dependencies using Bower

[rxaviers]

Manage the following frontend dependencies using a tool (eg. bower). Based on whole team discussion about a consistent way of managing frontend dependencies across all projects.

dependencies:

• jQuery Core (present on ./js);
• jQuery UI (present on ./js);
• jquery.hashchange (present on ./js); [1]

devDependencies:

• requirejs (present on ./external);
• QUnit (present on ./external);
• jshint (to-be-included);

1: About jquery.hashchange.js modification that is not yet upstream. Can we use @gseguin modified clone in the bower config, eg. "hashchange": "gseguin/jquery-hashchange"?

[arschmitz]

a couple things here. Qunit we want to be under dependencies along with jshint so that tests can be done without the users need to install bower or npm ( the jshint wont be until we switch to make our quint tests run it #6364 ).

As to hashchange. im not sure i have a strong opinion on this one way or the other.

[rxaviers]

a couple things here. Qunit we want to be under dependencies along with jshint so that tests can be done without the users need to install bower or npm ( the jshint wont be until we switch to make our quint tests run it #6364 ).

Updated jshint on the above list. About not needing to run bower or npm after git clone, you may want to commit the dependencies after being fetched I guess.

As to hashchange. im not sure i have a strong opinion on this one way or the other.

Good, because using bower now to point to @gseguin's branch (the same one of the upstream PR) has the benefit of making the future transition (for upstream lib) smoother.

[arschmitz]

@rxaviers yes sorry should have mentioned that yes we plan to commit the dependencies to maintain the ability to run tests and demos out of the box

[rxaviers]

:)