Sorry that you had to add it @alteredq.

Fixed TrackballControls, RollControls and PathControls not handling window resize. Commented out key event swallowing in FlyControl. Started to fix examples not dealing properly with 0 sized window on init.

See #2062

This white-on-white rendering wasn't really working.

Is as it was before, but I implemented the event dispatching in a different way (checking the distance of the object position between frames). Also renamed the 'update' event to 'change'.

controls.addEventListener( 'change', render );

Right now only misc_camera_trackball.html uses this.

At least till we don't have this solved somehow better I think we should keep the old one. New one makes everything using it feeling broken, it's distracting.

Moved new event-driven `TrackballControls` into `TrackballControlsExperimental`. For the moment used just in "misc_camera_trackball.html" example.

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.

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

Aargh, I feel dirty now.

This one was quite a pain.

Also added silly path camera example.

Fleshed out RollCamera: refactored code out of example, add more keyboard controls, API and made it framerate independent.