From beta.1 to beta.2, without the fuss
Good news: documented façade users keep their source code. Update the Cargo requirement, run your checks, and then enjoy the new retained and scrolling improvements.
The audited beta.2 delta removes or renames no documented beta.1 façade item. Most applications need no source migration.
01
Three small steps, then back to building
Treat the upgrade like a tiny pit stop. Keep your current code, change one version string, and let Cargo check the result.
Update Cargo.toml
Select 0.1.0-beta.2 explicitly in the façade dependency.
Run cargo check
Compile on Rust 1.88 or newer and review any warning from your own application.
Try the visible flow
Open your main window and exercise scrolling, dialogs, inputs, and reactive updates.
[dependencies]
ailloli_ui = "0.1.0-beta.2"02
One low-level exception to inspect
Applications built through the documented ailloli_ui façade keep their public names. A custom runtime integration may need one explicit invalidation request.
Using RuntimeHandle directly?
A service registered with RuntimeHandle::register_ui_service must request the required invalidation when it reports changed state. Context::register_ui_service already performs the owner-scoped Build request for you.
03
A few new toys to try
Beta.2 focuses on consistent retained updates and smoother interactive scrolling, while adding a handful of useful public hooks.
- Public scrollbar geometry and drag primitives for custom scrolling experiences.
- Composed retained dialogs with Dialog::modal_content and an Enter fallback through Dialog::on_submit.
- Configurable editor margins that keep the caret comfortably in view.
- Component render closures can capture the state they need.
- Custom widget authors can inspect the public LayoutPass contract.
04
Pack three reminders in your backpack
The upgrade is light, but beta software still deserves clear boundaries.
- Ailloli UI remains pre-1.0, so later beta releases may evolve the API.
- Confirm that 0.1.0-beta.2 is available on crates.io before using the registry dependency.
- Vulkan and OpenXR remain experimental and are not promises of hardware readiness.