InputNode readonly option

[sunag]

Not use uniform input if readonly is true in InputNode. ( for optimization )

in new THREE.Vector3Node( 1, 1, 1 ) instead use explicit declaration, for example:

// readonly = true
vec3( 1.0, 1.0, 1.0 )

// readonly = false (default)
uniform vec3 nV0;

Of course. readonly not allow change the value after build the shader material.

---

In NodeFrame I rename updateFrame to updateNode which is more suggestive but keeping updateFrame in nodes.

[sunag]

@mrdoob @WestLangley What do you think about rename the property coord to uv of TextureNode and CubeTextureNode?

[sunag]

Other thing... 'transform' is a position offset and normal is a normal offset.

[sunag]

'transform' is a position offset

my mistake. actually transform is a local position.
to create an offset, is need:

material.transform = new THREE.OperatorNode(
	new THREE.PositionNode(),
	displaceNode,
	THREE.OperatorNode.ADD
);

but normal is a normal offset. currently to create a normalMap is need:

mtl.normal = new THREE.TextureNode( getTexture( "grassNormal" ) );

but it could be like this:

mtl.normal = new THREE.NormalMapNode( new THREE.TextureNode( getTexture( "grassNormal" ) ) );

and allow normal slot to others customized NormalNode.

Are some thoughts...

[WestLangley]

mtl.normal should be renamed mtl.normalMap, but this looks like the right API to me:

mtl.normalMap = new THREE.NormalMapNode( new THREE.TextureNode( getTexture( "grassNormal" ) ) );

[sunag]

This doubt about normal came when add NormalNode in normal slot.

// following the logic. I think that it should work:
mtl.normal = new THREE.NormalNode();

[sunag]

however, mtl.normal is like as mtl.normalOffset in pratice

[mrdoob]

Minor thing: I don't think using these bitwise operations are worth it these days (speed vs readability).

[sunag]

Instead what do you recommend parseInt or Math.floor?

[sunag]

I think that Math.floor is "more" number-oriented.

[mrdoob]

Thanks!