Added FlyCamera (thanks to James Baicoianu). Added specular map to normal map shader. Added WebGL Earth FlyCamera demo.

Changed normal map shader to multiply specular component with diffuse weighting as specular highlights were appearing in the dark parts.

Changed camera look speed in minecraft and terrain demos, they were too fast - I guess as everything got faster with antialiasing off.

Reenabled antialiasing in few demos where it was too ugly without (basically anything with lines and without postprocessing).

Fixed again spurious invisible characters in empaempa's code (which are breaking everything and are hard to hunt as they look like spaces).

If you want to get edges, run converter like with "-e" flag:

python convert_obj_three.py -i model.obj -o model.js -e

Output seems to match Blender exporter.

There is a new class Edge which stores vertices and faces for edge (I wasn't sure if indices or references would be better, so at least for the moment it contains both).

Geometry now contains a list of such edges, created in JSONLoader, based on edge data exported from Blender.

From Blender we get a list of vertex index pairs, from which in Geometry.computeEdgeFaces() we compute faces which share this particular edge and store them in the Edge object.

Not sure if edges work properly till we don't have something using them. For now I just checked cube data exported from Blender and it seems fine.

Also did some whitespace cleanup here and there.

Updated GeometryUtils.merge with Face*.color changes.

Unfortunately C4D exporter is outdated and we don't use that. Removing it for now... Hopefully someone will re-port the Blender exporter again.

Also updated docstring for OBJ converter.

All WebGL examples should now work.

Getting closer though still having some junk data poping out here and there.

Work in progress, not expected to work yet.

(among other things, we don't deal yet with new vertex colors for particles/line/ribbons, for the moment they just use geometry.colors as before, also we need to specify which type of uvs to use somewhere, analogous to which type of vertex colors to use)

Gah, that was painful. Obvious solution with object.lookAt doesn't work, forward facing direction (heading and attitude) is fine, but banking gets messed up:( Tried many fixes, none worked, so I just resorted to simple rotation around Y-axis based on direction vector.

Spline control points shouldn't be cycled, this produces freaky behaviors near start and end of path. Instead they have to be capped.

Also did some refactoring.

Thanks to empaempa for spotting this ;)

Added translate( distance, axis ), translateX( distance ), translateY( distance ) and translateZ( distance ) methods to Object3D.
Camera3D translate method overrides Object3D's one. NoFly parameter removed (this should be handled from outside I think).

Object3D::lookAt works! (and Vector3.setRotationFromMatrix too!)

Next: Object3D::translate...

WebGLRenderer checks if texture is power of 2. Throws an error if it's not.

Animation.js - fixed scale bugs and removed flattenToArrayOffset
AnimationHandler.js - fixed so keyframes at same time is removed
Matrix4.lookAt - fixed so it handles situations where z === up and where eye === target
SkinnedMesh.update - added flattenToArrayOffset in end of update

Minor tweaks.

WebGLRenderer: renamed geometryChunks to geometryGroups :P

Mergable: WebGLRenderer.js: changed so camera.matrixWorldInverse is used instead of camera.matrixWorld.