1. Flyology TUI
  2. Components
  3. Progress groups

Feedback

Progress groups

Track typed jobs with determinate, indeterminate, and lifecycle states.

Generated previewCharm
Dedicated Progress groups example rendered in the Charm skin

The site build compiles the dedicated Ada component example, constructs Progress groups through its public API, and exports that exact styled surface. Read the capture source.

When to use it

Use progress groups for a bounded set of work items that need selection, aggregate progress, and distinct work states.

State and ownership

The Flyology_TUI.Components.Progress_Groups package defines this component.

Stable typed IDs survive reorder. Phase changes occur only when the application explicitly advances the model; no timer or task is retained.

  • The application model owner applies updates during serial event dispatch.
  • Appearance and skin values are borrowed only while the component renders.

Input and updates

Keyboard, wheel, and local mouse input select rows. Rendering can show rows or a deterministic segmented aggregate.

Integration sequence

  1. Create the bounded model and populate it with caller-owned data.
  2. Route the current keyboard or local mouse event through the component handler.
  3. Apply the typed result, then render from the updated model with the current appearance.

See the linked package reference for its exact declarations and contracts.

Responsive and accessible behavior

  • Use dimensions and regions from the current layout or presentation value.
  • When a component owns mouse capture, route its matching release even when the pointer leaves the original bounds.
  • Retain a glyph, label, border, or text-attribute cue when the terminal reduces color.