#6 may be too much of a hurdle, if we want people to actually use this in their browsers. getting the performance right might be a lot of work, and the yew/wasm UI feels really janky right now compared to the wasm UI.
i would still like for the environment to work with the DOM, however, using imgui wasm may be a good shortcut to be at least usable on the web.
probably not just plug and play because the current imgui adapter layer is doing event loop and glutin stuff, probably works differently in wasm. probably worth trying a clean wasm-imgui-rs project just to see what's involved.
#6 may be too much of a hurdle, if we want people to actually use this in their browsers. getting the performance right might be a lot of work, and the yew/wasm UI feels really janky right now compared to the wasm UI.
i would still like for the environment to work with the DOM, however, using imgui wasm may be a good shortcut to be at least usable on the web.
probably not just plug and play because the current imgui adapter layer is doing event loop and glutin stuff, probably works differently in wasm. probably worth trying a clean wasm-imgui-rs project just to see what's involved.