Draft
Conversation
…ering. Decouple Index.razor page from specific WasmHost implementation.
Change emulator renderer code for fragment shader rendering to work with both Silk.NET native and WASM. Shaders changed to be ES compatible (works in browser and native).
with WebGl (Silk.NET) rendering.
|
|
Another highly experimental experiment could be to utilize wasm-gfx. Although the API is still under heavy development with a 0.3 version it is in a somewhat usable state. It is expected that such application will be runnable both using software like wasmer and inside web browsers from a single source base. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Experiment with locally compiled experimental Silk.Net packages for Blazor WASM integration.
Probably won't be useable as is.