Tracking issue for WebGL / WebAssembly
Open
area-Meta
feature
tracking issue / epic
- Dominant language
- C#
- Stars
- 5.2k
- Forks
- 477
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 2
Description
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)
Contributor guide
Assessment
This issue has not been assessed yet.