bite-gp-runtime 1.24.401

Zed's process harness for starting and driving a GPUI application
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19

//! 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`.

#![warn(missing_docs)]

mod application;
mod pipeline;

pub use application::{Application, ApplicationHandle};
pub use pipeline::{FramePipelineExt, InstrumentedPipeline, PhaseMetrics, ThrottledPipeline};