wgpui 0.4.1

Independent wgpu + winit UI framework (community fork of GPUI / GPUI-CE 0.3.3)
Documentation

wgpui

wgpui is a hybrid-immediate/retained and GPU-accelerated UI framework for WGPU. It started as a community fork of GPUI / GPUI-CE 0.3.3 and keeps a GPUI-shaped programming model (App, Entity, Window, flexbox divs, actions) and renders through a unified wgpu + winit backend. However, it is not a drop-in for GPUI-CE git main or Zed GPUI: those trees have split crates, AccessKit, and different platform APIs. WGPUI versions on its own line.

The discriminating API is WgpuSurface: a double-buffered wgpu texture that lives in the UI tree. A CAD or 3D shell can render into WgpuSurfaceHandle::back_buffer_view(), call present(), and let WGPUI composite the result with quads, text, and paths. Surface resizes preserve the logical handle while versioning replacement texture views, so compositor bind groups remain valid through window and full-screen transitions.

Text services use a platform interface. Linux builds require Pango 1.50 or later, Cairo 1.18 or later, HarfBuzz and Fontconfig development libraries. The DirectWrite adapter requires Windows 10 build 15063 or later. Desktop text uses Core Text on macOS, DirectWrite on Windows, and Pango on Linux; release status records acceptance. Layout uses taffy. UI and monospace text default to the operating system's font families. Applications can override either family; framework assets contain no bundled text fonts.

Processed images and color glyphs use straight-alpha RGBA; native byte orders and premultiplied alpha are normalized at their producer boundaries. See GPU surfaces and capture for presentation, shared-device access and complete-frame readback.

Programming-model notes: docs/contexts.md, docs/key_dispatch.md.

This consolidated workspace also contains WGPUI Kit, an application façade and component library adapted from GPUI Kit 0.8.1. See STATUS.md for validation and release state and Kit engineering guides for current architecture, design, themes and selected examples.

Headless Linux rendering tests require a Vulkan implementation as well as the loader. On Debian and Ubuntu, Mesa software rendering uses mesa-vulkan-drivers, with libegl1 and libgl1-mesa-dri for the OpenGL fallback. Install vulkan-tools and run vulkaninfo --summary to verify adapter discovery before the real-renderer tests. A loader or development headers alone do not supply a software GPU implementation.

Usage

To install from crates.io once 0.4.1 is published, add this dependency:

[dependencies]
wgpui = { version = "0.4.1" }

To try an unpublished revision, clone the repository and use wgpui = { path = "../wgpui" } in your application’s manifest. Adjust the relative path to the checkout root. Cargo will use the framework and derive sources from that checkout.

See examples/learn/wgpu_surface.rs for embedding a wgpu render target, examples/learn/paths.rs for GPU paths, examples/learn/custom_drawing.rs for canvas drawing, and examples/legacy/hello_world.rs for a window.

WGPUI 0.4.1 requires Rust 1.100.0 or newer. Base 0.8.2 contains the companion virtual-list fixes. See the changelog for the framework and Base changes and the Kit compatibility guide for the public dependency and macro contracts.

The project compiler is pinned in rust-toolchain.toml; the release checklist describes the explicit, read-only stable-version check and review process.

License

The Rust framework uses Apache-2.0, with separately scoped MIT adaptations and a CC-BY-SA-3.0 example illustration. The aggregate package declaration is Apache-2.0 AND MIT AND CC-BY-SA-3.0; see LICENSE and scope notices. Original GPUI is copyright Nathan Sobo and Zed Industries contributors. This tree is maintained independently.

See licensing and source notices for the combined Apache terms, separately licensed material and open release-audit findings.