As per discussion in #1207

Shadow cascades should be now a bit more under control.

Cascades can't be active together with multiple separate shadows, it's either one or the other. For this there is `renderer.shadowMapCascade` parameter.

Made colored shadow frustum debug visibility toggleable via `renderer.shadowMapDebug` parameter.

Fixed runaway globals in ShadowMapPlugin.

Fixed missing Gyroscope dependency in WebGL lib build.

As per discussion in #1170

This should make it work with cameras having parents other than scene root.

Added a silly check on Object3D.add(). It's a quick check and it avoids enless recursivity making the browser silently hang.

Not sure about this hardcoded epsilon thing for "isZero", also related strict equality check. Maybe these should be configurable somehow.

Now we can just do console.log(THREE.VERSION). Thanks for the suggestiong @chandlerprall!

After shadow mapping fixes orthographic shadow projection finally started to work.

Work in progress. Still need to figure out some way to set up shadow camera automagically with respect to the actual camera (so that whole scene is shadowed when the camera moves). For the moment shadow camera needs to be handled manually (like for SpotLight).

This is for seeing how camera actually looks (frustum, line-of-sight, up), it's not a camera. Not sure about the name.

Plus added "onUpdate" callback handling also for cube textures.

Updated Closure compiler. Added more verbose compile warnings. Fixed all compile warnings. Started to fix runtime warnings in examples.

For verbose compile warnings to be practical I had to add externs and disable some warnings manually (there were tons of complains about "global this" and "cannot instantiate non-constructor"). Other solution would be to annotate explicitly constructors all over the code base.

(prompted by John Carmack's praise of static code analysis http://altdevblogaday.com/2011/12/24/static-code-analysis/)

With a little twist - per color component mixing of regular and wrap-around lightings.

As per @toji's "don't lie to WebGL about your format" recommendations in WebGL Camp 4 talk (http://media.tojicode.com/webglCamp4/#19).

Work in progress. For the moment works just with CTMLoader. Still not sure where some pieces of code would go.

Upsides:
	- initialization time cut down significantly (1.8 seconds => 0.7 seconds for CTM example)
	- much smaller GL buffers thanks to fully used indexing (Walt has 6x less vertices)
	- consequently much smaller memory footprint all around, both for main and GPU memories,
	  which means less swapping and better vertex caching

Downsides:
	- can't have anymore sharp per-face effects like flat shading (at least if mesh is not constructed in a way where each face has own vertices)
	- can't have multiple materials per mesh
	- no more easy manipulation of anything (for the moment actually no runtime manipulation at all, typed arrays are just thrown away, dynamic geometries code path not yet implemented)

As per Giles recommendation here http://learningwebgl.com/blog/?p=4379

Doing normalization of normals / binormals / tangents in fragment shader instead of vertex shader. This seems to help with artefacts appearing in certain models with OpenGL rendering backend.

Also added modulating environment reflection by specular map.

Implemented again @ekitson's improvement to GeometyUrils.center. Increased light intensity in loader_json_blender example.