Update to TS 0.9.5; add logic to include static properties.
Add Touch 2.3.1.
adding explicit any
Work around incorrect property type for xtype in Sencha docs.
Fix typo in 2.2.1 file name.
changed [illegal] variant type usage to a prefered static typing
removed access of non-existant property
removed duplicate identifier 'update'
Update angular-scenario.d.ts

'enter' lacks return-type annotation, implicitly has an 'any' return type
Restify: updated plugin defintions, allowed --noImplicitAny compile flag
node-ffi: adopt for --noImplicitAny
update
Merge branch 'master' of https://github.com/mapsjs/DefinitelyTyped

Conflicts:
	mapsjs/mapsjs.d.ts
update
Added TypeScript Definition files for Html2Canvas

Added TypeScript Definition files for Html2Canvas - a library for taking
screenshots of a browser window.
[Node] Node attaches errno information to some exceptions.

This is valuable information for Node applications that need to figure out why a particular system call failed.

Note that errno can either be a string or a number, which is why I have typed it as 'any'.

While this is undocumented, it is tested:
Code property: https://github.com/joyent/node/blob/v0.10.23-release/test/simple/test-fs-open.js#L34
Errno property [string]: https://github.com/joyent/node/blob/v0.10.23-release/test/internet/test-dns.js#L148
Errno property [number]: https://github.com/joyent/node/blob/v0.10.23-release/test/simple/test-domain-implicit-fs.js#L43
Syscall property: https://github.com/joyent/node/blob/v0.10.23-release/test/simple/test-stdout-close-catch.js#L38
Path property (I can’t find a test, but many examples have this line): https://github.com/joyent/node/blob/v0.10.23-release/deps/npm/node_modules/fstream-npm/example/bundle.js#L6

..and well supported in the code for all platforms (this is where I got the name 'ErrnoException' from):
*nix: https://github.com/joyent/node/blob/v0.10.23-release/src/node.cc#L719
Windows: https://github.com/joyent/node/blob/v0.10.23-release/src/node.cc#L856

Unfortunately, while every errno exception is guaranteed to have the ‘errno’ and ‘code’ properties (see the logic in the source code in node.cc), there is no hard guarantee that particular library functions will always pass an ErrnoException to the callback. I cannot find a counterexample at this moment, though. Since we can’t have union types in TypeScript, I simply made all of the properties on ErrnoException optional as a compromise.

I am only adding modifications to the fs module, which definitely throws ErrnoExceptions. But according to the examples above, other modules (e.g. dns) also pass errno information back to applications. People familiar with those other modules can update their typings to reference this interface when applicable; I lack the experience with those modules to update their typings.

Further proof:
```javascript
$ node
> var fs = require('fs');
undefined
> fs.open('doesntexistlol', 'r', function(e) { console.log(Object.keys(e)); console.log(e.code); console.log(e.errno); console.log(e.path); });
undefined
> [ 'errno', 'code', 'path' ]
ENOENT
34
doesntexistlol
```
Merge pull request #1443 from butlersoftware/knockout---TypeScript-0.9.5-fixes

various knockout test fixes
Merge pull request #1446 from GaryB432/explicit-any

adding explicit any
Merge pull request #1447 from damianog/patch-6

Update angular-scenario.d.ts 'enter' lacks return-type annotation
Merge pull request #1449 from ufon/master

Restify: updated plugin definitions, allowed --noImplicitAny compile flag