Fixes #1866

Fixes #1866

Also added rudimentary position-based vertex colors to MarchingCubes object and example for testing.

There is no normalization or anything, it's up to application layer not to set colors beyond <0,1> range.

This addresses issue #1834

removing less necessary stuff from Path.js. May still have to decide whether to migrate to using .curves from .actions

As per suggestion in https://github.com/alteredq/three.js/commit/5d5f92d6411f3d39725ea704594d7a09ecb92cca

Fixed MarchingCubes bug introduced by previous commit. Added flat shaded material to marching cubes example.

Only these 4 are actually valid for regular textures:

http://www.khronos.org/opengles/sdk/docs/man/xhtml/glTexImage2D.xml

We had it wrong before, it just accidentally worked as default type GL_UNSIGNED_BYTE is common for both data types and pixel types.

Also added optional quick-and-dirty UVs for MarchingCubes object, just to be able to test this. For the moment these are just XZ world coordinates.

This should address half of #1834

I struggled with this for quite a while, but I think this should be the right thing - having convenience methods for switching between the scene/world/global/absolute coordinates to the local/child/relative coordinates right with Object3D, which is part of the scene graph, rather than the Vector class.

Related issues: #1752, #1043, commits 025fb624 and baf0f65e

As per discussion in #855

To be tested if it works ...

See discussion here: https://github.com/alteredq/three.js/commit/2fd0b1b14deef40825d6a853ae0522f78d4b57d8