Remove optionalTarget - part 6

[WestLangley]

As proposed in #12231.

[mrdoob]

Thanks!

[WestLangley]

@Mugen87 @mrdoob @zz85

Ugh... I have run into a road-block with all the curve classes (and parametric geometries, apparently).

The curve classes are 2D/3D-agnostic. So one is unable to modify the codebase to pre-allocate the Vector2/3 targets, because there is no way to know in what dimension the user operating.

So, as it stands, part of the library/examples still support optionalTarget, and it is due to the getPoint() method -- and related methods.

[Mugen87]

Yeah, I remember this when I've added serialization/deserialization.

One approach that might solve the problem is to add a flag to all curve classes that indicate their respective vector space. Curve.getPoints() could look like this:

getPoints: function ( divisions ) {

	if ( divisions === undefined ) divisions = 5;

	var points = [];

	for ( var d = 0; d <= divisions; d ++ ) {

                var point = this.is2D ? new Vector2() : new Vector3();

                this.getPoint( d / divisions, point )

		points.push( point );

	}

	return points;

}

But i'm not sure how nice this is.

[WestLangley]

Maybe we should have 2D- and 3D-specific classes, instead.

[Mugen87]

Do you mean something like Curve2D and Curve3D? That would mean for example:

Curve2D -> LineCurve
Curve3D -> LineCurve3

[WestLangley]

Yes. Just a thought...

Curve -> LineCurve
Curve3 -> LineCurve3

[WestLangley]

Oh, wait... I meant

Curve and CurvePath (2D-only)

Curve3 and CurvePath3 (3D-only)