Flow and algorithm

Platform spec article

Flow and algorithm

Back to Console controls ◎ Open feature in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

ADRs (2)

1. 0040-character-cell-layout Character-cell layout only Accepted

   Console controls operate on cell grid, not pixels.

   Context

   Terminal UI in corelib targets TTY character grids.

   Decision

   Rule	Detail
   Coordinates	Rows/columns in character cells
   Graphics	Pixel graphics are out of scope

   Consequences

   Layout helpers align with Console.ConsoleSize and resize events.

   Verification anchors

   Console control tests under packages/console.

   Open full ADR page

2. 0041-livetick-caller-owned-loop LiveTick caller-owned redraw loop Accepted

   Periodic redraw uses LiveTick; callers own fiber/channel loops.

   Context

   Corelib should not embed a full UI framework inside controls.

   Decision

   Rule	Detail
   Tick	LiveTick drives periodic redraw
   Loop	Callers compose fibers/channels around tick

   Consequences

   Interactive samples pair LiveTick with concurrency package channels.

   Verification anchors

   Console controls examples and tests.

   Open full ADR page

Articles

• Contracts and edge cases Layout and redraw requirements for console controls. article Standard Reviewed Thu May 21
• Design model Control tree, render context, and character-grid layout. article Standard Reviewed Thu May 21
• Examples Panel and progress bar render patterns. article Standard Reviewed Thu May 21
• Flow and algorithm Frame render and live tick loop. article Standard Reviewed Thu May 21
• Verification and traceability Control layout tests and module paths. article Standard Reviewed Thu May 21

History

0 revisions (git unavailable at build; counts may be empty)

Open full history on GitHub

No commits recorded for this path.

Completeness

OKfeature · 3 SpecSection(s) · 1 H2 heading(s)

Section id	Required	Found
what-this-feature-specifies	yes	yes
implementation-anchors	yes	yes

Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).

Related spec docs

• Feature
  Console controls

  Parent feature hub

• Feature
  Console terminal events

  Resize-driven relayout

Purpose

Document flow and algorithm for the Console Controls feature: role-specific normative detail beyond the feature hub.

Canonical references

• Feature hub: Console Controls
• Sibling articles in this bundle (design model, contracts, flow, examples, verification)

Detailed behavior

Single frame

1. save ← EmitDec("7")
2. Optional Erase.DisplayAll when clearing screen
3. Walk control tree → append styled/plain segments to buffer
4. restore ← EmitDec("8")
5. System.Output.Write(buffer)

Live tick loop (sketch)

1. Create Channel<ConsoleMessage> via Console.MessagesChannel()
2. Fiber loop: Console.RunTick(channel, lastSize) → may enqueue Resize
3. On message: if Resize, invalidate layout; call Frame.Render
4. Yield or sleep between ticks (host policy)

Cursor/erase sequences: ANSI escape model.

Verification

See the verification and traceability article in this bundle and compiler/corelib/beskid_corelib/tests/corelib_tests/src/console/.

Related topics

• Parent feature hub and Terminal and console area