GPUI Kit

One dependency for building desktop applications with GPUI:

[dependencies]
gpui-kit = "0.6"

gpui-kit depends on the matching set of GPUI crates, so an application never lists GPUI itself. use gpui_kit::*; is GPUI, and each layer is reachable by name:

gpui_kit::application() opens the platform and gpui_kit::init() initializes the enabled layers:

use gpui_kit::component::button::*;
use gpui_kit::component::Root;
use gpui_kit::*;

struct Hello;

impl Render for Hello {
    fn render(&mut self, _: &mut Window, _: &mut Context<Self>) -> impl IntoElement {
        div().child(Button::new("ok").primary().label("Let's Go!"))
    }
}

fn main() {
    gpui_kit::application().run(|cx| {
        gpui_kit::init(cx);
        cx.spawn(async move |cx| {
            cx.open_window(WindowOptions::default(), |window, cx| {
                let view = cx.new(|_| Hello);
                cx.new(|cx| Root::new(view, window, cx))
            })
            .expect("failed to open window");
        })
        .detach();
    });
}

The gpui-component features (inspector, decimal, tree-sitter, tree-sitter-languages, and each tree-sitter-<language>) are available on gpui-kit under the same names. test-support turns on GPUI's test harness for #[gpui_kit::test], TestAppContext, VisualTestContext, and native-platform rendering support; enable it under [dev-dependencies]. It also exposes gpui_kit::test::{TestWindowExt, TestAppContextExt, TestSupportExt, ElementSnapshot} for UI integration testing: render real components in headless windows, simulate input, and verify state, focus, layout and application callbacks. gpui_kit::TestSupportExt is also available without the feature: .test_support() keeps production render chains intact and returns the original element in normal builds. Snapshots read native accessibility properties without hand-supplied state. See UI integration testing for usage. The independent profiler feature enables GPUI frame-event instrumentation and is off by default. See https://gpui-kit.com for the guides.