Tracking issue for WebGL / WebAssembly

[HurricanKai]

This issue partially relies on the idea of (GL) API interfaces.

• [In Progress] Emscripten (-> theoretically possible for 2.0 but quite unlikely [sponsor us 🙂])
  • [In Progress] Initial Blazor WebAssembly version allow as-is running of existing OpenGL(ES) programs using the Emscripten OpenGL support
  • [In Progress] Use Emscripten GLFW & SDL to support Windowing
• [Not Started] JavaScript (this is the true WebGL, the above "simply" cross-compiles "normal" GL code to WebGL (-> guaranteed 3.0)
  • [Not Started] Look at how to implement function loading backed by I(InProcess)JSRuntime (-> Is it worth it supporting the async JSRuntime here [-> Blazor Server], I don't think so right now)

[sps014]

• [Not Started] Look at how to implement function loading backed by I(InProcess)JSRuntime (-> Is it worth it supporting the async JSRuntime here [-> Blazor Server], I don't think so right now)

Currently IJSInProcessRuntime is only implemented for Blazor WASM because Blazor Server runs in a separate process from the Browser. dotnet/aspnetcore#37926

I think blazor Server not worth supporting as of now.