Enable wasm, when it works #30
Conversation
| let Ok(mut clipboard) = arboard::Clipboard::new() else { | ||
| return; | ||
| }; | ||
| #[cfg(not(target_arch = "wasm32"))] |
There was a problem hiding this comment.
we should be able to use this as an alternative:
https://rustwasm.github.io/wasm-bindgen/api/web_sys/struct.Clipboard.html
There was a problem hiding this comment.
Or:
https://github.com/aweinstock314/rust-clipboard
Which seems to support wasm?
There was a problem hiding this comment.
yeah I think Clipboard is going to work. Its necessarily async which is a bit of a pain since EventWriters, Commands, etc are going to get moved out of the loop (and can't be) but worst-case scenario I think we can AsyncTask it.
There was a problem hiding this comment.
Took a look at it tonight. TaskPool::scope would work (and is seemingly the Right Way) for passing the EventWriter in and such... except that it panics when awaiting the clipboard future.
This seems like a long-standing issue: bevyengine/bevy#1924
I pushed up some code that gets the clipboard text, but its not working as we'll need a workaround for scope not panning out.
There was a problem hiding this comment.
#ecs says use a channel so I'll do that
wasm support with webgpu is not a tier-1 support target for vello, but it does work.
RUSTFLAGS is required for egui, which could be moved out of dependencies. I opted to try to keep development simple since the crate is prerelease rather than putting everything behind features and such.
I'd propose a support angle that is: "if it works in bevy_vello, it should work in woodpecker", so as to avoid bugs that are clearly not woodpecker related from becoming a support burden.
webgl2 support is not a possibility, so we're only talking about webgpu here.
good news
a bunch of things work already, such as modals, transitions, and clipping.
screenshot-2024-07-29-at-19.48.27.mp4
screenshot-2024-07-29-at-19.49.43.mp4
Potential work