Major breaking changes tracking

[Doprez]

Purpose

This issue will be an overview of planned changes that will be breaking to Strides core. This will allow us to consolidate discussions, PRs and issues into a single place for future planning.

Current PRs

• Requirements for fully custom Game runtime management #2404 likely going to be closed in favour of Reformat startup WIP #2574
• Reformat startup WIP #2574 The main PR related to changing the core startup and surface rendering of Stride

Current Discussions

• Stride Windowing Changes #2524 The discussion related to strides startup changes
• System.Numerics or Stride.Math #2210 Tracking for talks about changing to System.Numerics

Tasks

TBD I will fill this out better with breakdowns for what is needed to get going on the above discussions

Math

• Deprecate Stride math extensions in favour of System.Numerics
• Change core math types to the System.Numerics equivelent
• Add Implicit conversions to System.Numerics

Game startup

• Change to a more robust GameWindow
• decouple the GameWindow from GamePlatform maybe in favour of something that defines just the update/render loop?
• remove GameContext it serves no real purpose and just adds an unnecessary layer. Should use GameSettings instead
• remove cyclical dependencies between systems, discussed here
• Move Game.IsMouseVisible out of the GameWindow and into the Input library.

Graphics

• Drop support for DirectX 9 / OpenGL 2.0 #2186

branch chores

• Make a new dedicated branch for proper testing (5.0?)

[Jklawreszuk]

You can also add my two PRs which can be considered as breaking change:

• Drop support for DirectX 9 / OpenGL 2.0 #2186
• fix : Metrics - Remove all data collection from Stride.Engine #2261

[Doprez]

I added the directx 9 and opengl 2 support to the main checklist but I think @xen2 wasn't convinced to remove metrics last I remember?

I also dont think its a breaking change so Im not sure that we would need to wait for 5.0 if we wanted to merge that in.