TSL: Color Space revision

[sunag]

Description

Examples:

// with parameter

node = node.toOutputColorSpace( THREE.SRGBColorSpace );
node = node.toWorkingColorSpace( THREE.SRGBColorSpace );

// without parameter -- it's will use `renderer.outputColorSpace`
// this turn more security the conversion of `sRGB` or `DisplayP3` to `linearSRGB` and vice versa.
// the user does not need to worry about the output display to work with color space conversions

node = node.toOutputColorSpace();
node = node.toWorkingColorSpace();

• Improve TSL ColorSpace
• Revision currentColorSpace
• Added currentToneMapping

[github-actions]

📦 Bundle size

Full ESM build, minified and gzipped.

Filesize dev	Filesize PR	Diff
685.4 kB (169.7 kB)	685.4 kB (169.7 kB)	+0 B

🌳 Bundle size after tree-shaking

Minimal build including a renderer, camera, empty scene, and dependencies.

Filesize dev	Filesize PR	Diff
462 kB (111.4 kB)	462 kB (111.4 kB)	+0 B

[sunag]

@WestLangley I improve the names to linearSRGB instead of just linear as you suggest in X d0f9425

[donmccurdy]

Note that for wide-gamut rendering, Linear-sRGB will not necessarily hold the role of "working color space", we'd instead want to render in Linear P3, Linear Rec. 2020, or perhaps ACEScg. That's not an urgent concern right now... but I wonder if naming with that "working color space" term might be more future-proof?

const outputNode = node.fromWorkingColorSpace( targetColorSpace = renderer.outputColorSpace );
const linearNode = node.toWorkingColorSpace( sourceColorSpace = renderer.outputColorSpace );