wgpui-base
Unstyled behavior and infrastructure for WGPUI applications, adapted from Longbridge GPUI Kit v0.8.1. wgpui-base 0.8.2 uses WGPUI 0.4.1 and requires Rust 1.100.0 or newer. Base and the framework use independent version numbers.
Use WGPUI Kit for the application facade, or wgpui-component for ready-to-use styled controls. Use wgpui-base if your application should own its visual styles while reusing interaction, focus, accessibility, animation, virtual lists, and theme tokens.
Version requirements for the candidate, once published:
[]
= "0.4.1"
= "0.8.2"
For source development, the framework is at the repository root and Base is at crates/wgpui-base. Source and application imports use the canonical wgpui and wgpui_base names. See the Kit compatibility guide.
Where it fits
application
├── wgpui-component Complete, styled framework experience
└── custom UI Application-owned design system
└── wgpui-base Interaction, state, and infrastructure (this crate)
Dependencies point from higher layers toward the foundation: wgpui-base does not depend on wgpui-component.
Design Principles
- Behavior belongs to the foundation: click handling, keyboard activation, controlled state, focus, accessibility roles, and infrastructure.
- Presentation belongs to the application: layout, size, color, spacing, radius, borders, shadows, variants, and animation.
- Semantic APIs come first: themes expose tokens such as
primary,surface, anddestructive. - wgpui-native composition: controls implement
StyledandParentElementand work with the fluent builder API.
For example, Button::new("save") has no padding, background, radius, or size by default. Being unstyled is an explicit API contract, not a missing feature.
Initialization
Call wgpui_base::init(cx) once before creating windows or using foundation controls. If the application already calls wgpui_component::init(cx), do not call base init again.
use *;
use wgpui_base as _;
Optional Features
| Feature | Enabled by default | Purpose |
|---|---|---|
decimal |
No | rust_decimal::Decimal values in plot scales |
inspector |
No | Inspector support in WGPUI and wgpui_derive |
test-support |
No | Framework support for deterministic UI tests |
Quick Start
use *;
use Button;
;
An ElementId must remain stable within a view so wgpui can preserve focus and element state.
Controlled State
Checkbox, Radio, Switch, and Toggle are controlled components. Their callbacks report the next value; the application updates its own state and passes that value back on the next render.
Semantic state styles layer in a fixed order: builder chain, then value states (checked, pressed, selected, focused), then disabled last.
Capability Overview
Unstyled Controls
| API | Behavior provided |
|---|---|
Button |
Click and keyboard activation, focus, disabled and selected states, and the Button accessibility role |
Checkbox / CheckboxIndicator |
Checked, unchecked, and indeterminate states with corresponding accessibility semantics |
Radio / RadioGroup |
Radio activation, focus, and a grouping container |
Switch / SwitchTrack / SwitchThumb |
A controlled switch with independently styled track and thumb parts |
Toggle / ToggleGroup |
A controlled pressed state and grouping container |
Link |
Link semantics and activation with an application-provided open_with navigation strategy |
Table and semantic table parts |
Table, row-group, row, column-header, cell roles, and accessibility indices without layout or styling |
Toast / ToastStack / ToastManager |
Alert semantics, lifecycle, timers, limits, measured stack geometry, and interaction-aware motion |
Text Editing
| Control | State | Use |
|---|---|---|
Input |
InputState |
Single-line values, masking, validation, and number stepping |
Textarea |
TextareaState |
Ordinary multi-line text, fixed rows, wrapping, and auto-grow |
Editor |
EditorState |
Source code, highlighting, gutter, folding, decorations, diagnostics, and LSP integration |
Focus, scrolling, animation, themes
FocusTrapElement,InteractiveElementExt,ElementExt,FocusableExtScrollbar,v_virtual_list/h_virtual_list,AutoScrollmotion::transition(preferred) and legacyanimation::TransitionTheme/SemanticThemeTokens/StyledExt
Base includes NavStack, History (browser-style trail), and UndoHistory (grouped undo/redo). Root owns window-scoped layers and presentation plugins. The input module guide describes the shared editing engine; the Kit compatibility guide explains the byte-offset editor contract and stable Ropey API.
Development
From the consolidated WGPUI repository root, using Rust 1.100.0 or later:
Related
- wgpui-component
- WGPUI Kit guide
- wgpui
- Published wgpui-base documentation (candidate documentation follows publication)
- Upstream Longbridge GPUI Kit
License
Apache-2.0. See LICENSE-APACHE for the license and Longbridge attribution. Upstream notices are preserved.