1. Flyology TUI
  2. Components
  3. Text areas

Editing

Text areas

Edit bounded multiline Unicode text with selection, history, and wrapping.

Generated previewCharm
Dedicated Text areas example rendered in the Charm skin

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

When to use it

Use a text area for multiline input, notes, source, or a composer. Use streaming text for non-editable append-only output.

State and ownership

The Flyology_TUI.Components.Text_Areas package defines this component.

A limited model owns normalized LF text, cursor, selection, bounded undo history, viewport, and capture. If capacity is insufficient, the operation leaves state unchanged.

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

Input and updates

Grapheme-aware keys, page movement, wheel scrolling, click-drag selection, paste, undo, and redo share one state machine.

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.