Add vector and matrix utility functions

[axeljaeger]

Utility functions as discussed in:
https://forum.babylonjs.com/t/matrix-vector-color-conversation-and-utilities-cleanup/49818

[bjsplat]

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

[deltakosh]

Isn't it a code duplication of what we already have?

[axeljaeger]

Yes as mentioned in the forum, this is code duplication of Matrix.ComposeToRef, unfortunately I don't know how to reuse the existing code. Maybe ComposeToRef could make use of this version, but then you would have the + offset with an offset of 0.

[bjsplat]

Snapshot stored with reference name:
refs/pull/15101/merge

Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15101/merge/index.html

To test a playground add it to the URL, for example:

https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15101/merge/index.html#WGZLGJ#4600

Links to test babylon tools with this snapshot:

https://playground.babylonjs.com/?snapshot=refs/pull/15101/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/15101/merge
https://gui.babylonjs.com/?snapshot=refs/pull/15101/merge
https://nme.babylonjs.com/?snapshot=refs/pull/15101/merge

To test the snapshot in the playground with a playground ID add it after the snapshot query string:

https://playground.babylonjs.com/?snapshot=refs/pull/15101/merge#BCU1XR#0

[bjsplat]

Visualization tests for WebGPU (Experimental)
Important - these might fail sporadically. This is an optional test.

https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15101/merge/testResults/webgpuplaywright/index.html

[bjsplat]

WebGL2 visualization test reporter:

https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15101/merge/testResults/webgl2playwright/index.html

[sebavan]

I am not to sure what those new functions bring ?

Is it just a coding style preference ?

[axeljaeger]

Hi Sebavan,
the original idea was to add some functions that are not yet in the library, such as Vector2.toVector3, that feel missing because there is already a similar function, such as Vector3.toVector2.

As Deltakosh mentioned in the discussion, for the sake of tree-shaking, we should actually not put more functions in Vector and Matrix, but rather add them to the mentioned utility functions file, so I prepared this MR as a base of discussion.

Actually, personally I got unsure wether it is worth filling this file utility file already with the missing functions while the majority of this functions remains for now in Vector an Matrix classes respectively.

When it is about making the functions pure functions and not part of the classes I can also easily add them somewhere in my project.

What do you think?

[sebavan]

Hi Sebavan, the original idea was to add some functions that are not yet in the library, such as Vector2.toVector3, that feel missing because there is already a similar function, such as Vector3.toVector2.

As Deltakosh mentioned in the discussion, for the sake of tree-shaking, we should actually not put more functions in Vector and Matrix, but rather add them to the mentioned utility functions file, so I prepared this MR as a base of discussion.

Actually, personally I got unsure wether it is worth filling this file utility file already with the missing functions while the majority of this functions remains for now in Vector an Matrix classes respectively.

When it is about making the functions pure functions and not part of the classes I can also easily add them somewhere in my project.

What do you think?

I completely agree that new addition should be in this file and this format, but here I am more questioning the general usefulness of those shortcuts and how frequently we would use them to understand if it justifies the extra maintenance and weight in the UMD scenario :-)

@deltakosh @RaananW any thoughts?

[sebavan]

Lets keep them in your project for now and reopen if we change our mind then ?