PhysicsPlugin refactor

[CedricGuillemet]

Goal of this PR: move physics to v1, add v2 folder. keep existing working (back compat).

All current physics moved to physics/v1. New stuff in physics/v2. Shared things are in physics/

• v1 and v2 have different names (body/shape/material/constraint in V2 and impostor/joint in V1) and different concepts
• Have an helper PhysicsAggregate that will contain a body, a material and a shape that can be created by 1 call (just like existing v1)

On the Babylon side, Material, shape, body are opaque proxies. Real work is done in the plugin. Plugin stores its references thanks to public _pluginData: any = undefined;

PhysicsViewer, mesh,....still using v1.

Tested with PG from documentation and PhysicsDebug Viewer.

[azure-pipelines]

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.

[azure-pipelines]

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.

[azure-pipelines]

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.

[azure-pipelines]

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.

[azure-pipelines]

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.

[azure-pipelines]

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.

[azure-pipelines]

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

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

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

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

Links to test babylon tools with this snapshot:

https://playground.babylonjs.com/?snapshot=refs/pull/13279/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/13279/merge
https://gui.babylonjs.com/?snapshot=refs/pull/13279/merge
https://nme.babylonjs.com/?snapshot=refs/pull/13279/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/13279/merge#BCU1XR#0

[azure-pipelines]

Visualization tests for webgl2 have failed. If some tests failed because the snapshots do not match, the report can be found at

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

If tests were successful afterwards, this report might not be available anymore.

[RaananW]

I'll review it fully tomorrow morning. The first thing I noticed - there is no need to add V1 or V2 to the exported modules. Importing the right ones from the right directory will be enough when developing core. for UMD users there will be a conflict if they are named the same. For that you can use export A as B, similar to the way this is exported:

https://github.com/BabylonJS/Babylon.js/blob/master/packages/dev/gui/src/3D/controls/index.ts#L24

[sebavan]

Before I deep dive in the PR, the main question is how big of a breaking change it is for the existing users both UMD and ES6 users ?

[CedricGuillemet]

Before I deep dive in the PR, the main question is how big of a breaking change it is for the existing users both UMD and ES6 users ?

This is a question for @RaananW as I don't want to say incorrect things

[sebavan]

@RaananW any update on the back compat ?

[RaananW]

Sorry! totally missed the question.

Yes, this is a breaking change for the es6 users, since the files have moved.
We can fix it by placing proxy files that export from the right places (but are not exported in any index.ts). this way we solve the issue after moving it. does it make sense?

Of course, another solution is to only have a v2 folder and move the v1 files back to their original position.

[sebavan]

@RaananW and @CedricGuillemet, I let you chose as I do not have any preferences but would like one or the other if possible :-)