Liora's public GPUI component prelude.
liora-components exports the visual and interactive controls used by the
native Gallery and Docs applications: form controls, overlays, navigation,
data display, charts, code blocks/editors, virtualized data views, and small
utility widgets.
Application setup
A GPUI app should initialize Liora once during application startup:
use gpui::App;
use liora_components::init_liora;
fn setup(cx: &mut App) {
init_liora(cx);
}
The high-level liora_components::init_liora(cx) entry point initializes
Liora core/theme state, global component services, and the app-level key
bindings needed by inputs, text/code selection, overlays, Preview, Tour, and
picker popups. Use liora_components::init_liora_with_mode(...) for an
explicit Light or Dark startup mode.
Stateful controls
Controls with focus, selection, open state, or text value should normally be
stored as gpui::Entity<T> fields in a parent view. This preserves state
across GPUI renders. Gallery and Docs are the maintained examples for this pattern.
Architecture boundary
Liora components render native GPUI element trees. This crate does not require Tauri, WebView, HTML/CSS, DOM, or a browser runtime.