1. Flyology TUI
  2. Components
  3. Tabs

Navigation

Tabs

Switch stable-ID pages with responsive clipping and persistent active state.

Generated previewCharm
Dedicated Tabs example rendered in the Charm skin

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

When to use it

Use tabs for sibling views at one hierarchy level. Keep application-wide commands in a menubar.

State and ownership

The Flyology_TUI.Components.Tabs package defines this component.

The model retains active and focused IDs. An immutable presentation maps visible tab regions after clipping.

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

Input and updates

Arrows move focus, Enter and Space activate, and matching mouse release activates the pressed tab.

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.