diff --git a/RELEASE-v0.9.md b/RELEASE-v0.9.md index ec0252088..ed8d1eceb 100644 --- a/RELEASE-v0.9.md +++ b/RELEASE-v0.9.md @@ -68,6 +68,9 @@ for examples of idiomatic ways to write code for Xous. - Initial support of emulation of EC - No COM-based inter-chip communication yet +## New in 0.9.1 +- `modals` server for a simple "Pure Rust" API for creating dialog boxes and getting user input. See the `tests.rs` file for some examples how to use the applcation calls. + ## Roadmap to 1.0 The items that are still missing before we can hit a 1.0 release include: diff --git a/services/gam/README.md b/services/gam/README.md index 73323a2ca..16894a22c 100644 --- a/services/gam/README.md +++ b/services/gam/README.md @@ -213,9 +213,16 @@ between "fully visible", "partially visible", and "fully obscured" states. TextEntry is specifically coded so that its payload is cleared upon send, so that plaintext passwords are not left hanging around in the heap or stack. +The `modals` server allows applications to pop up generic modals without having +to write all the eventing glue code to the GAM. The server has the following properties: +- "Does about the right thing" for 90% of the applications +- Shared between multiple processes with a lock -- so the messages from this server should not be absolutely trusted +- Currently implements notifications, progress bars, text input, radio buttons, and checkboxes. +- Has a "pure Rust" blocking API so routines can sequence through the dialog boxes in a declarative fashion without having to write fancy sequencing logic. + Example code: - - The `rtc` server contains an example of a modal that is dynamically modified with several states, and uses the helper mechanism. - - The `root-keys` server contains an example of a static password modal, and uses an explicitly coded helper thread. + - The `rtc` server contains an example of a modal that uses the `modals` server. + - The `root-keys` server contains an example of a static password modal, and uses an explicitly coded helper thread. It manages its own modals because it has a unique rendering property that can only be summoned by this process. ### Helper Threads