support of global compilation mode on top of commonJS

[b-laporte]

This small PR introduces a new compilation option called mode that allows to choose between "commonJS" and "global":

// default mode is "commonJS"
// default globalRef is "hsp" (only used when mode is "global")
var r = compiler.compile(sample.template, "template1", {mode:"global", globalRef:"foo"});

In practice this change cannot be used yet as we have to package and distribute the hashspace runtime as a global variable first (e.g. on ariatempaltes CDN). But when this is done, I would be in favour of putting "global" as default compilation mode (of course hashspace Getting Started should be updated accordingly)

Note: I chose to have an enum type for mode as I guess we will want to support "es6" as a new mode soon, so a basic boolean was not enough...

[coveralls]

Coverage increased (+0.1%) when pulling 822b483 on b-laporte:hsp-global into 729511f on ariatemplates:master.

[benouat]

I am fine with this PR.
Nevertheless, I think we should investigate the road of universal module definition, so we don't have to bother the end-user with a compilation option...

They could simply use the lib the way they feel comfortable, and it could work automagically.

PS: @b-laporte I am glad you change you mind about "global" being the default one !

[PK1A]

+100 (wow, I never thought I will be happy from the fact of introducing global variables :-)). In the longer run I think we shouldn't need this mode switch at all as we could go with the UMD definition:

• http://know.cujojs.com/tutorials/modules/authoring-umd-modules
• https://github.com/umdjs/umd
• http://addyosmani.com/writing-modular-js/

I've started to look into Browserify a bit and it can surely package things using UMD. I guess we will need some fiddling with the build options, but sounds feasible for now.

[PK1A]

One more observation - fixing compiler is not enough since the transpiler generates require for the json.$set dependency.