Epic: Render Pipeline #306
Labels
No labels
Blocked
Duplicate
MoSCoW/Could Have
MoSCoW/Must Have
MoSCoW/Should Have
Points/1
Points/13
Points/2
Points/21
Points/3
Points/5
Points/8
Priority/Backlog
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
State/Completed
State/In progress
State/In review
State/Paused
State/Unverified
State/Verified
State/Wont Do
Type/Bug
Type/Epic
Type/Feature
Type/Legendary
Type/Task
Type/Testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Reference: aethyr/Aethyr#306
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Background and Context
The Terminal UI Framework (#112) needs a render pipeline that transforms RenderOps into actual terminal output. The pipeline processes ops through multiple stages — routing, formatting, layout, dirty checking, ncurses rendering, and compositing — to produce efficient, flicker-free terminal updates. The pipeline targets 20 FPS with dirty-checking optimization and supports a headless mode for testing.
Expected Behavior
RenderOps drained from the render queue flow through a 6-stage pipeline that ultimately produces ncurses screen updates. The pipeline is designed for efficiency (skip unchanged windows), correctness (proper layout solving), and testability (headless renderer for tests).
Acceptance Criteria
Child Issues
All child issues for this epic are tracked as individual issues with dependency links.
Definition of Done
This issue is complete when all child issues are merged to
masterand the Render Pipeline is operational.