Module render_backend 

The render backends a binary carries, how a launch picks one, and the render-world system that drives a renderer drawing offscreen.

The core names no backend. Each one registers a RenderBackend into the app’s RenderBackends while the app is built, from its own crate, and a launch path asks the registry for what the app’s configuration names: one backend by name, or every backend in priority order so a launch can fall through to the next one when the first cannot start. A binary that does not link a backend has no entry for it, which is how an app pays only for the renderer it uses. The registry is the one every backend kind shares; see crate::backends.

Structs

RenderBackend

One render backend: its name, its rank under auto, and how to make its renderer.

Functions

install_offscreen

Put renderer, already attached to a crate::traits::FrameTarget::Offscreen image, into app.

Type Aliases

RenderBackends

Main-world registry of the render backends this binary carries. A backend’s capability install adds itself with crate::backends::register_backend.