holger-ui 0.1.1

Operator/admin UI for holger over the HolgerObject core API — egui via facett, embedded (LocalHolger, direct core calls) or remote (RemoteHolger gRPC).
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26

//! # holger-ui
//!
//! An operator/admin UI for [holger](https://codeberg.org/nordisk/holger).
//!
//! The UI is built in two layers:
//!
//! * [`data`] — the transport-agnostic **view-model**. It drives the core
//!   [`traits::HolgerObject`] API (satisfied by `LocalHolger` for direct,
//!   in-process rust calls into holger core, or `RemoteHolger` over gRPC) and
//!   turns each response into a plain view struct that exposes `state_json()`.
//!   This is the "render-from-data / see-what-the-user-sees as data" law: the UI
//!   can be driven and asserted headlessly with no display and no egui. It is
//!   the default build and carries the unit tests.
//!
//! * [`app`] (behind the `gui` feature) — the egui presentation, built from
//!   [facett](https://codeberg.org/nordisk/facett) components, mirroring the
//!   nornir-viz idiom (one blocking core call per UI action on a private
//!   current-thread runtime).
//!
//! Both layers are generic over `Arc<dyn HolgerObject>`, so the same UI runs
//! embedded (no network) or against a remote holger server.

pub mod data;

#[cfg(feature = "gui")]
pub mod app;