Expand description
GPUI’s process harness: how an application is built, configured and started.
Application is what a host program holds in order to bring GPUI up — the
main function of a desktop app, or an embedder driving its own run loop.
Everything an application is once it is running lives in
gpui_authoring, which this crate drives rather than contains. So do the
test and bench harnesses: they build a real gpui_authoring::App and drive
real frames, so they stay beside the code they exercise.
The gpui crate is a thin facade over both, so applications keep importing
gpui.
Structs§
- Application
- A reference to a GPUI application, typically constructed in the
mainfunction of your app. You won’t interact with this type much outside of initial configuration and startup. - Application
Handle - A strong handle to an
Applicationstarted withApplication::run_embedded. - Instrumented
Pipeline - Times the root passes of the pipeline it wraps, recording into the
PhaseMetricsthe caller holds. - Phase
Metrics - What an
InstrumentedPipelinehas measured. - Throttled
Pipeline - Defers frames that arrive sooner than a target rate.
Traits§
- Frame
Pipeline Ext - Composition for pipelines.