Expand description
Retained terminal interfaces compiled from fusor HTML.
Re-exports§
pub use services::ServiceLimits;pub use services::Services;
Modules§
- coherent
- Staged scene publication for fusor’s executor-independent coherence protocol.
- layout
- Dirty-frame layout and painting; the retained scene owns identity and lifetimes.
- native
- Native terminal ownership and the bounded, wake-driven input loop.
- services
- Local tasks, monotonic timers and bounded workers for one application owner.
- style
- The bounded terminal stylesheet data emitted by
hypercmd-build. - text
- Unicode policy shared by text measurement, painting and editing.
Structs§
- Controller
- Focus, editor gestures and hit testing for one retained scene.
Call
decoratebefore output, andpresentedonly after that output succeeds. - Editor
State - Byte offsets refer to extended grapheme boundaries; scroll offsets are terminal cells.
- Error
- A recoverable update leaves its committed subtree unchanged.
- Event
- Key and scroll events visit the target then its ancestors until handled.
- History
- In-memory screen history, shared by a router and its nested views. Retains at most 64 locations; pushing after Back discards forward history. Handles do not extend the supplying owner’s lifetime.
- Modifiers
- Node
- Stable identity. A retained handle becomes inert when its owner is disposed.
- Scope
- A prepared component. Publish only after all fallible preparation succeeds.
- Static
Node
Enums§
- Error
Kind - The boundary at which preparation or interaction failed.
- Event
Payload - Input
- Host-normalized input. A reported paste is always one text edit.
- Key
- KeyKind
- Kind
Constants§
- VERSION
- Hypercmd’s generated runtime contract, independent of fusor’s contracts.
Traits§
- Component
- Implemented by generated HTML in the component’s own Rust module.
- Event
Result - Event handlers may return either
()or a recoverable error.
Functions§
- mount
- Prepare a reusable component as an application root, without activating it.