emberry kernel-driver separation
devensiv opened this issue · comments
Create a system that allows us to isolate the tauri ipc and frontend activity from the core crate
What we need:
- loader (bin): marks the entry point for the rust backend which loads the "kernel" crate
- kernel (lib): is home to all the program logic, uses "driver" crate to subscribe/emit frontend events
- driver (lib): has frontend implementation specifics for subscribing/emitting events and provides an opaque wrapper type for the frontend in use which will be passed into "kernel" by "loader"
Crate name suggestions:
loader
emberry-loader-tauri
emberry-tauri-startup
kernel
emberry-core
emberry-kernel
driver
emberry-driver-tauri
emberry-com-tauri
emberry-tauri-link
emberry-bridge
cherry
fibre