* Camera is now a base object. PerspectiveCamera should be used instead. Figured out a way to show a warning when misused.
* OrthoCamera is now OrthographicCamera.
* Removed `target` from Camera.

Misc
* Renamed Trident to Axes.

Seems like calling `renderer.initWebGLObjects` out of regular frame render doesn't play well with new buffer switching minimization optimization.

Found out that CrosseyedWebGLRenderer probably wouldn't work for target-less cameras.
Something weird going on with `webgl_scene_test.html` and `webgl_scene_test_blender.html`. For some reason cubes dissapear.

Removed QuakeCamera.

Removed _gl.clear call from WebGLRenderer's .setSize().

Implemented .autoClearColor .autoClearDepth .autoClearStencil as per @alteredq's suggestion at #587.

* Camera.useTarget is now false by default. Updated some of the examples. I tried to remove target altogether (and use lookAt every frame), but I found that WebGLRenderer's ShadowMaps uses a camera with target. Will try again at some point.
* Object3D.lookAt now checks if it's a Camera and does the inverted view.
* Quaternion glitch reported at #595
* Added .name to Material
* WebGLRenderer .clear() to .clear( color, depth, stencil ). All of them true by default.

New stuff:

- car rig
- dynamic cube maps
- drop shadows from geometries
- tilt-shift
- motion blur
- fxaa

Uses shrunk lens flare texture from ro.me.

Works better in OpenGL with thick lines. Single pixel wide lines in ANGLE get a bit of strip pattern.

Added "lower level" immediate rendering functionality. The existing mechanism requires modification of the WebGLRenderer for different objects. The new implementation leaves the current MarchingCubes immediate renderer intact but checks for existence of a immediateRenderCallback member function of the object. If found, that object is added to the scene.__webglObjectsImmediate array. The program, webgl context, and frustum are currently passed into the callback, putting al rendering responsibility at the implementing object. This may break the Three.js abstraction somewhat, but allows "power users" to do some funky webgl stuff while still relying on the Three.js framework for the rest of the scene...

Finally 60 fps on 5,000 monkeys ;)

All examples should work.

Should not refresh anything if material doesn't change for several objects in a row (in a single frame).

Hope this didn't break something, I remember this being tricky. Went through examples and they seem to work ok, gained some fps in performance test.

Also disabled sorting in depth-of-field example for some more fps gain.

Still didn't figure out the original reason for recent fps drop in performance / dof examples :/

Similarly like for geometry groups, iterating over object properties turned out to be bottleneck for some use cases: gained 5-10 fps in depth-of-field example (which btw for some reason got slower recently).

Added ability to disable render passes to EffectComposer. Added simple blend shader to ShaderExtras.