Merge pull request #388 from MagicMau/master

Updated Underscore.js and added underscore-ko.js
Added EntityManager.hasChangesChanged event

EntityManager.hasChanges event was renamed to EntityManager.hasChangesChanged in v1.1.0
Update breeze-tests.ts

Changed hasChanges event to hasChangesChanged as it was renamed in v1.1.0
Merge pull request #399 from jlerasmus/master

Added EntityManager.hasChangesChanged event
Added typescript definitions for trunk8
updated the trunk8 def.
Merge pull request #401 from niemyjski/master

Added definitions for trunk8
Removal of logChange method and explanation

logChange is an example of an extension, not part of the standard library. To add extensions, simply extend the interface outside of the definition file:

interface KnockoutExtenders {
    logChange(target: KnockoutObservableAny, option: string): KnockoutObservableAny;
}
Merge pull request #402 from Steve-Fenton/patch-3

Removal of logChange method and explanation
Definition for jquery.eLang - Language Learning application.
Merge pull request #404 from sumegizoltan/master

jquery.elang definition
Definition of bgiframe for IE6 - simple plugin implementation without jQuery.
Merge pull request #405 from sumegizoltan/master

Definition of bgiframe for IE6 - simple plugin implementation without jQuery.
New definition of jquery.tagsmanager plugin.
AngularJS: fixed typing of the ng.IPromise.then function

The type definition for ng.IPromise.then was, in my opinion, incorrect
semantically, and breaking on practical examples in my codebase.

An `IPromise`' `then` function takes a callback which is called with the
value of the promise once it's fulfilled. This could be a number, a
string, some object, an array of strings, anything really. Yet the
typing in angular.d.ts specified `then` as taking a `successCallback` of
type `(response: PromiseCallbackArg) => any`.

The definition of `PromiseCallbackArg` seems very permissive at first
glance, as it is defined to be an object with a bunch of fields, all
optional. Any object, a number, and a string all type check correctly
with such a type, but an array of strings, for example, does not
(`cPromise` in the provided list of test).

Furthermore, it seems to me that the `PromiseCallbackArg` definition was
added specifically to support the response type for promises returned by
the Angular `$http` service, the `ng.IHttpPromise`.

So instead of having an incorrect type on the `ng.IPromise.then` function,
I propose we return it to its generic form, and instead override the
type of the inherited `then` function in the `ng.IHttpPromise` interface.
This would also warrant renaming `PromiseCallbackArg` to
`IHttpPromiseCallbackArg`.
Merge pull request #407 from anchann/master

AngularJS: fixed typing of the ng.IPromise.then function
Changed reject to be 'any' per angular docs
Merge pull request #410 from jwcarroll/master

Updated IDeferred.reject per Angular docs
Update definition file for durandal.d.ts

- Make applicationHost parameter optional in setRoot
- Add missing activeRoute definition
- Add missing useConvention definition
- Add missing handleInvalidRoute definition
- Change mapRoute definition so you can pass an URL with all the other
parameters as you will usealy do or you pass a RouteInfo object without
having to give it any other parameter. moduleId, name and visible are
now optional.
Add backgroundpositionClass to definition

Add backgroundpositionClass to ToastrOptions interface