Tait Hoyem
Tait Hoyem
First attempt at Axum-style state management. The final PR should have: - [x] Routers for `atspi::Event` - [x] Handlers for `atspi::Event` - [x] Routers for `OdiliaCommand` - [x] Handlers for...
Oh the wonderful works of binding keys in a Wayland world! Especially those pesky [activation keys](https://github.com/xkbcommon/libxkbcommon/issues/425#issuecomment-1951747358) that have no equivalent outside of screen readers (see that thread and its links...
Speech dispatcher does not start automatically, and our current methods don't appear to wake it up. Running `spd-say 'hi'`, followed immediately by `cargo run` appears to work. So let's find...
How should the Odilia remote extension work? Do we send all AT-SPI events? All Odilia events on how to speak? How do we handle keybindings being sent? etc. My assumption...
State management is an extremely difficult problem for screen readers. Axum's method of handling state is somehow quite ingenious. Especially since we could run multiple handlers concurrently (or in parallel)...
At this time, Rust's type system is not being used to verify (before the program starts) that the configuration file is correct. Error with the JSON are far too common,...
Right now, under either the `main` or `mother-of-all-refactors` branch, we appear to have an issue where the cache isn't quite *guaranteed* to be correct based on the order of events....
In an effort to make state management teste, I've realized that directly modifying global state may be somewhat problematic in the long term. This issue is to "purify" each function...
We should have tests for any type of event which can be passed to `odilia/src/events/mod.rs::dispatch`, which is currently around 175. We absolutely need tests to detect what changes are made...
We could have a dedicated communication thread between the SR and plugins—which is running on a blocking task. Basically: `Plugin Comm. Thread SR` The comm thread will also be how...