hearth
hearth copied to clipboard
hearth-rs
Shared execution environment for constructing 3D virtual spaces from the inside.
Decouple the *Abi structs from all the plugin and factory code, so that `lib.rs` contains Hearth integration code and the new "abi.rs" file would contain low-level Wasm integration code only.
Windows obviously does not support Unix Domain Sockets, which is what Hearth uses for IPC. What else can we use? The obvious 1-to-1 equivalent is TCP. Thoughts?
Until we can get #175 fully fleshed out and implemented, let's just implement some stub IPC code that gets Hearth to compile on Windows even if IPC doesn't actually do...
Depends on #184. We can just make a job matrix in the workflow file and set up CI to build and test on Windows too. Someone with some Windows CI...
Right now, if a process running in a terminal quits, the guest has no way of knowing about it. We have a few ways of fixing this: - Polling: add...
The current terminal emulator demo screenshot is cool but not the best hook for Hearth, since while it represents the "self-modifying" part of Hearth, it doesn't include the "virtual world"...
The plugin and runtime builder systems were not changed much in the flue pr so they did not get the documentation overhaul that everything else did.
Update the `wasm` protocol with an error enum (even if only a placeholder) and `SERVICE_NAME`.