tui: tracking — loom-tui v0.1.0 roadmap & implementation order #47
Labels
No labels
area:agents
area:ai
area:config
area:dashboard
area:design
area:design-review
area:devtools
area:entities
area:gallery
area:generate
area:image
area:infra
area:meta
area:model-browser
area:navigation
area:presets
area:security
area:sessions
area:settings
area:sharing
area:test
area:ux
area:webhook
area:workdir
type:bug
type:chore
type:meta
type:user-story
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
charles/loom#47
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?
Purpose
Meta / tracking issue for the
loom-tuiinitiative. Source of truth for implementation order and PR stacking strategy. Sub-tickets are in theloom-tui v0.1.0milestone and referencespecs/loom-tui-specification.md.Recommended implementation order
Implement in the phases below. Each PR stacks on the previous; don't skip phases — earlier tickets set up the traits and plumbing later tickets assume.
Phase 1 — Foundations (serial; unblock everything else)
tui.tomlconfiguration file supportPhase 2 — Image rendering (can start after #11; parallelisable inside)
Phase 3 — Generate screen
Phase 4 — Gallery screen
Phase 5 — Model browser
Phase 6 — Entities, presets, settings, sharing, devtools
Phase 7 — CI, packaging, tests
just run-tuirecipe & Forgejo Actions CIPR stacking policy
mainfor the first ticket in a phasetui/<short-slug>-<issue-number>(e.g.tui/scaffold-11,tui/kitty-renderer-12)Closes charles/loom#Nmainuntil the reviewer OKs the overall shape; subsequent PRs in the same phase rebase as neededjust qamust pass before requesting reviewIssue index
See milestone loom-tui v0.1.0 for the full list.
Phase 8 — Backend Integration (glue layer)
All Phase 1–7 tickets (#11–#46) built UI scaffolds. These tickets wire every screen/overlay to loom-core's actual backends (PluginBridge, GalleryStorage, AiJobWorker, event bus).
Implementation order
Foundations first (#84, #85), then screens can be wired in parallel:
Dependency graph
#84 and #85 are serial (everything depends on bootstrap). After those, #86–#96 are parallelizable — each wires a different screen/overlay independently.
Status update — post-#129
Significant progress across phases 3, 4, and 5 from a series of recent rewrites. Re-checking against the phase list:
✅ Done / functionally covered
ratatui-image(#119); kitty/sixel/halfblock auto-detection handled by the crate.rat-widgetTextArea (real cursor, selection, clipboard, word wrap).🟡 Partial / needs follow-up
replay_params()exists but no key binding (ticket still open).🔴 Still open as filed
Cross-cutting issues filed since this tracking ticket
The following weren't in the original phase list and should be folded in for the v0.1.0 push:
These are all infra-level and probably belong in a "Phase 8 — polish" before tagging v0.1.0.
New batch from GTK↔TUI parity audit
Filed 16 follow-up tickets covering all gaps identified in the audit. Suggested implementation order (top to bottom, by value-per-effort):
Quick wins (small, high-impact)
replay_params)Mid-size features
Large features
Phase 8 — polish (already in roadmap)
Each ticket is self-contained with acceptance criteria, references to GTK code, and out-of-scope notes — designed for AI agent pickup.