Skip to main content

Module traits

Module traits 

Source
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§

pub use crate::task::Spawn;
pub use crate::task::Timer;

Structs§

A11yBridgeFactory
Builds the accessibility bridge for a window once the window exists.
FrameRequest
What the caller knows about the frame it is asking for.

Enums§

FrameTarget
Where a Renderer puts its frames.
RenderError
Why a renderer could not bind to its target or put a frame on it.
WindowError
Why a window backend could not run the app.

Traits§

A11yBackend
The bridge between the ECS world and the platform accessibility API.
Bindable
Declares that a Component participates in the entity-property bus exposed by crate::property_store::PropertyStore.
LayoutEngine
A layout engine: what turns the styled tree into absolute boxes.
RenderTarget
A live OS window a Renderer presents into.
Renderer
A render backend’s renderer: everything between the retained scene and the pixels.
WindowBackend
A window backend: the OS window, the event loop, and the translation of platform events into the app’s messages.