Skip to main content

Crate oxidelake_tui

Crate oxidelake_tui 

Source
Expand description

Terminal dashboard built on ratatui + crossterm (docs/SPEC.md §2.7).

The application is a state machine decoupled from rendering: AppState + AppState::on_key are pure and unit-tested; render() is a pure function of (state, model, frame); run_terminal is the only place that touches a real terminal, and it brackets every repaint in a DEC 2026 synchronized update so PTY tests observe complete frames.

Panels: Plan DAG (hardware tag per operator), Inspector (selected operator’s counters), Telemetry (memory tiers, PCIe/NVMe rates) and Describe (column profiles). Keys: ↑/↓ select, Tab cycles panels, q quits.

In v1 the dashboard observes the local process only (a DashboardModel built from the session’s TelemetryHub).

Dependency direction: depends on oxidelake-core only.

Re-exports§

pub use app::NON_INTERACTIVE_TERMINAL_MESSAGE;
pub use app::draw_frame;
pub use app::is_interactive_terminal;
pub use app::key_input_from_crossterm;
pub use app::run_terminal;
pub use model::ColumnProfile;
pub use model::DashboardModel;
pub use model::demo_model;
pub use render::render;
pub use state::AppState;
pub use state::KeyInput;
pub use state::Panel;
pub use state::Transition;

Modules§

app
The real-terminal event loop (crossterm) with DEC 2026 synchronized updates.
model
The data the dashboard renders: a TelemetrySnapshot plus column profiles, and the synthetic fixture the demo binary and snapshot tests use.
render
Pure rendering: render(state, model, frame) draws the four panels and never reads a clock or any global, so the same inputs always produce the same frame.
state
Pure application state for the dashboard.