Conversation
This is basically the wasm-pack demo.
Embeds xilem_web into the blog, does counter demo.
The idea is that these should be generated by CI, but that's not in place just yet.
This should build the WASM for the Rust code, but hasn't been validated. At least the check build should work on PR upload.
Contributor
Author
|
Ok, I've now added CI, which does successfully build the wasm, but the deployment is not tested. It looks like wasm-bindgen is sufficient, I don't think the wasm-pack wrapper is actually needed. |
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
1 participant
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.
This adds a very basic xilem-web integration into the blog. Currently I'm using
wasm-pack --target webto build the wasm, then copying rust_demo{.js,_bg.wasm} into static/rust. These steps would be done by CI.Note that the Vello web demo is a bit similar. It uses wasm-bindgen directly, and that might be more lightweight; in this case, it's likely wasm-pack is a pretty thin layer around it.
This branch currently has no interesting content. The plan is to import the interactive demo from raphlinus/fast-stroke, along with nicer UI for controlling the experiments (currently, my main workflow is editing the code).