Expand description
The seam between the boundary and whatever builds the tree.
The boundary entry points, the batch arena, the theme and window records, assets,
messages, notifications, streaming appends and the frame request all belong to this
crate and behave the same whatever authoring model produced the tree. What differs is
how a tree is built and changed: a Dioxus VirtualDom diffs one, a recomposition
runtime re-runs the scopes that read a changed state. That part is a Runtime.
An application registers one with LaunchBuilder::launch_runtime, and every
compose_rust_host_* call is answered by a Host that drives it. Nothing about
the boundary changes with the runtime: the same five entry points, the same records,
the same batch.
Structs§
- Batch
- One batch, written by the runtime and by the Host into the same arena.
Traits§
- Runtime
- What builds and changes the tree, seen from the boundary.