Don't break the Windows' EOL.

I still don't see why this was here... Fixes #38.
Merge pull request #39 from dduponchel/issue38

Don't break the Windows' EOL.
File specific compression settings.
Added documentation for file specific compression
Added code to pass unit tests
Merge pull request #42 from amarcu5/patch-1

File specific compression settings.
Replace all mentions of old .add API with .file
Merge pull request #47 from Stuk/change-add

Replace all mentions of old .add API with .file
Lazy decompress data

This commit aims to be as lazy as possible :

When reading a file, we now don't decompress the content, we just keep
a reference to the original compressed file and an offset.

If the user accesses a file, we will decompress it and replace the
content (so we don't have to decompress it again).

When generating a zip, if a file has not been decompressed we check if
we can reuse the compressed content.

This unfortunately means that we won't be backward compatible : the
data attribute may not be calculated yet. Worse, the data now can be a
string, an array or a UInt8Array. The user must use the getters !

The interface for compression/decompression has also changed : we now
specify the input type for each operation.

This has been tested in IE 6 -> 10, firefox, chrome, opera.
If anyone has an apple product with safari, he's welcome to test :)
Replace the INFLATE/DEFLATE implementations

Use https://github.com/imaya/zlib.js instead of an old implementation.
Update documentation

Add the optimizedBinaryString option and hints about performances.
Tests : better display of unexpected errors.
inflate/deflate : v0.1.6
optimize memory consumption instead of cpu consumption

str += 'char' is faster than array.push && array.join but the difference
is not big.
String are immutable so the concatenation will create n(n-1)/2 objects,
so a memory consumption in O(n^2). The array join is in O(n).
When working with large files (hundreds of Mb), O(n^2) is clearly not a
good idea.

Also, use TextDecoder if available to boost perfs.
remove an old file
Avoid if possible strings manipulation.

Working with strings consumes a lot of resources. For example, the
transformation utf8 string -> binary string is faster with the path
utf8 string -> Uint8Array (via TextEncoder) -> binary string.
performances : small gains on chrome

See http://jsperf.com/array-direct-assignment-vs-push/31, direct
assignment is faster than push.
Merge pull request #56 from dduponchel/WIP_perfs

Improve performances
Add support for nodejs Buffer.

Tested with node-qunit and nvm for older versions. The tests pass with
nodejs >= 0.7.0.

This should fix the issue 46.
Throw an error when adding an unsupported object

This fixes #54.