This allows, for example, better integration of additively blended materials with a regular scene.

Not to be confused with depthTest (which controls complete access to depth buffer, including reading).

Also messed up a bit with particle emitter example.

Masking was real pain to get working with multiple render targets :/.

Unfortunately this introduced dependencies on MaskPass.js and ShaderPass.js even for use cases that do not use masking. Bah, will need to figure out some better way for deployment.

Cause everywhere there are warnings about not writing to the same texture which is also being read. Curiously enough this didn't make problems so far (save for mysterious lines when doing "heat" effect in ro.me).

Also updated dynamic particles example to handle resizing.

Added generic ShaderPass. Removed SepiaPass, ScreenPass, VignettePass. Added bleachbypass shader. Simplified multi-composer pipeline in postprocessing example.

Added dot screen shader / effect. Extended postprocessing demo. Fixed viewport bug for render targets.

Not sure yet about names and location of files.

Updated Tween.js (thx @jeromeetienne)

For some reason Chrome canary 12.0.713.0 doesn't have "window.WebGLRenderingContext".

Updated builds and README.

Also for the moment reverted autoupdate of canvas based textures. This breaks things and proper fix seems to require more efforts :(

Also updated GUI-DAT (didn't help with recent Chrome compositing bugs, though this is Chrome Windows issue), added FileAPI to Detector and fixed aspect ratio bug in WebGLRenderer.

Refactored everything to use CamelCase naming for properties. Plus some smaller fixes here and there.

Went through all examples, all should work.

JSON files exported from Blender / converted from OBJ files still use underscored property names internally. I don't know, should these also be changed?

Thanks to @mikaelemtinger ;)

That was much tougher than expected. No wonder other WebGL video demos around the web are broken.

Firefox OpenGL / ANGLE and Chrome OpenGL were ok, getting it to work in Chrome ANGLE was rather tricky.

Please report if something got broken. I tried to go through all textured examples but I may have missed something.

If you want to refresh texture on WebGL side, you just set "texture.needsUpdate" flag (if you use Loader or ImageUtils.loadTexture / loadTextureCube everything is taken care of).

Flag has to be set also for canvas-based textures, sorry no escaping this :(. I tried and it lead to ugly problems (e.g. AO minecraft demo mixes several asynchronously loaded and generated images into one texture, with autodetect always something was broken).

"needsUpdate" should work also on cube textures, though it's not tested yet (also there I didn't put hack for Chrome ANGLE).

	build/Three.js - Includes all renderers + extras
	build/custom/ThreeCanvas.js - Canvas renderer only
	build/custom/ThreeDOM.js - DOM renderer only
	build/custom/ThreeSVG.js - SVG renderer only
	build/custom/ThreeWebGL.js - WebGL renderer only
	build/custom/ThreeExtras.js - Extras only

Moved `THREE.Detector.js` to `examples/js/Detector.js`.

Updated examples to reflect these changes.

Firefox doesn't like Typed Array constructors without explicit sizes.

Also in Firefox there were some weird artefacts in Perlin noise when using Int8Array (patterns were repeated across diagonal lines).