Expand description
The backend roles, plus the Bindable trait declaring a component as a property-bus participant.
Each role is a trait a caller drives without naming an implementation. A WindowBackend runs the app and
drives a Renderer and an A11yBackend through their traits; a LayoutEngine installs the systems that
solve layout. Implementations register themselves into the registry of their kind (see crate::backends), and
the launch picks from there.
Re-exports§
Structs§
- A11y
Bridge Factory - Builds the accessibility bridge for a window once the window exists.
- Frame
Request - What the caller knows about the frame it is asking for.
Enums§
- Frame
Target - Where a
Rendererputs its frames. - Render
Error - Why a renderer could not bind to its target or put a frame on it.
- Window
Error - Why a window backend could not run the app.
Traits§
- A11y
Backend - The bridge between the ECS world and the platform accessibility API.
- Bindable
- Declares that a
Componentparticipates in the entity-property bus exposed bycrate::property_store::PropertyStore. - Layout
Engine - A layout engine: what turns the styled tree into absolute boxes.
- Render
Target - A live OS window a
Rendererpresents into. - Renderer
- A render backend’s renderer: everything between the retained scene and the pixels.
- Window
Backend - A window backend: the OS window, the event loop, and the translation of platform events into the app’s messages.