Anaglyph and ParallaxBarrier could also be merged somehow, as the only change is the fragment shader.

See discussion here: https://github.com/mrdoob/three.js/commit/6e002f324a06f6f766b50c930732a9994fdd4ac6#commitcomment-1234473

I tried to move BinaryLoader to /examples/js but SceneLoader needs it.
Curious to hear what people thinks about this change.

This probably could be done in some nicer way, but at least there is no more direct dependency in WebGLRenderer (and lib shrunk ;).

This is required for SSAO. Unfortunately scene.overrideMaterial is not enough for proper depth pass. Like for shadow maps, shader animated objects (like morphs) need different depth materials than static objects.

Now we can do things like this:

controls = new THREE.TrackballControls( camera );
controls.addEventListener( 'update', render );

Sadly, some examples are slightly broken until we have better pipeline for assets load complete event dispatching.

Also updated build script to fill in missing dependency (ImageUtils => DataTexture).

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.

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

Keeping the old IcosahadrenGeometry and OctahedronGeometry to double check results later.

It's Object3D subclass that takes a position from the scene graph hierarchy but uses its local rotation as world rotation.

It works like real-world gyroscope - you can move it around using hierarchy while its orientation stays fixed with respect to the world.

As per discussion here: https://github.com/alteredq/three.js/commit/835b57addaf328412b61a2b644ff5efd7fe6d25e

Sidenote: these extra verbose Closure warnings are starting to pay off - I keep catching subtle bugs (like missing dependencies in rarely used code corners).

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

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/)

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)

This should allow attaching of lights to objects. As a side effect, directional lights positions don't need to be normalized explicitly anymore.

Also changed viewport dimensions passed to render plugins to work with render targets with different dimensions than the screen framebuffer.

And fixed new dependencies in build script.

Because TortoiseGit suddenly refuses to make single commit with added and changed files :/

Work in progress. Still just experimenting. Probably will make some auto-adding of plugins.

Still a bit dirty but less than it was before. Maybe also sprites could be pluginized.

It's going to be handy for the WebGLRenderer (__webglObjects)

Got tired of redoing deltas all the time. Not sure about API or implementation details, but so far seems to be useful.

In future, we could for example have clocks that are slower / faster than realtime, or fixed step based.