feat(GUI): Tauri / Svelte migration #39
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
GUI Migration EFRAME & EGUI to Tauri & Svelte
Why
I've had a lot of issues with the design on the native eframe/egui setup. It felt really hacky to do "basic web layouts" and since I've done a lot of web things including front-end stuff, using Tauri, Svelte and Tailwind just felt right and way easier to design.
Commits & Changes:
fix(common): Client side set_colors takes responsibility of the bit scaling
feat(ffi): Impl Zig, Deno, Go examples of the FFIs and Justfile recipes to try them
chore(ffi): Better functions definitions
fix(colors): Better XY - RGB conversions
feat(ble): New reverse-engineered GATT UUIDs to try
feat(gui): The GUI backend now has a "command" to initialize the Devices state sync thread and sends its data with an event emmiter
fix(gui font): Changed OTF to var TTF for flexibility
fix(cli): Fix crash when setting a color with the old broken color converter
feat(gui): Impl storage save thread loop
feat(ffi): Set color RGB is now available
wip(ci): Commented out GUI build for the moment
feat(gui): Impl bt device search stream with events
TODO To match the previous GUI state: