wasm support to run geomedea in the browser #6
Conversation
michaelkirk
force-pushed
the
mkirk/async-zstd-rs
branch
13 times, most recently
from
4a794b3 to
a959e58
Compare
|
By way of an update, you can now see the examples from There's still some fleshing out to do - in particular I still need to handle non-string properties, but I think I should be able to wrap it up "soon" (like in the next couple days). |
michaelkirk
force-pushed
the
mkirk/async-zstd-rs
branch
2 times, most recently
from
0e96aee to
913d536
Compare
relocate their definitions to a more neutral location
michaelkirk
force-pushed
the
mkirk/async-zstd-rs
branch
from
913d536 to
8ce5bd1
Compare
The `zstd` crate we used for reading and writing zstd does not support wasm. The (pure rust) `ruzstd` supports wasm, but only supports reading. So we now use `ruzstd` for reading, and `zstd` for writing. So, writing is not supported on wasm, only reading. Introduces a javascript API in the new geomedea-wasm package (based on `wasm-pack new geomedea-wasm`)
michaelkirk
force-pushed
the
mkirk/async-zstd-rs
branch
from
8ce5bd1 to
f355203
Compare
|
Ok - I think this is ready to go. Let me know if you want any help trying this out. |
|
Disclaimer: it currently depends on a forked version of |
|
Also note that in the meanwhile there was a breaking change to the format in #7 So you'll need to regenerate any geomedea with the latest version of |
This is a bit hack-and-slash at the moment, but I can run some demos in browser now, which is neat.