Hare/yoi
1
1
Fork 0
Code Actions Packages Releases Activity

ticket: require panel aligned columns

Browse Source
This commit is contained in:
Keisuke Hirata 2026-06-06 17:36:49 +09:00
parent 1de5a9aac4
commit 9a3693d2f0
No known key found for this signature in database
2 changed files with 29 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
.yoi/tickets/open/20260606-060548-workspace-panel-layout-display-tuning/item.md
View File

@ -7,7 +7,7 @@ kind: task
priority: P2
labels: [tui, ticket, orchestration, panel, ux]
created_at: 2026-06-06T06:05:48Z
updated_at: 2026-06-06T06:06:30Z
updated_at: 2026-06-06T08:36:49Z
assignee: null
legacy_ticket: null
---
@ -27,6 +27,14 @@ Refine the workspace panel layout, labels, ordering, and displayed detail so the
- Follow existing TUI visual conventions/components.
- Preserve the single `yoi panel` route and no-Ticket Pod-centric behavior.
- Keep the UI intermediate representation thin; do not move authority into rendering code.
- Rework row rendering into stable, aligned columns rather than sentence-like rows.
- Ticket/action rows should put short, fixed-ish fields first and move the long Ticket title to the end.
- Example column order: marker/selection, priority/action/status/phase/id-or-slug, then title.
- The exact set can be tuned, but the long free-text title must not be the leading column.
- Pod rows should likewise put short, alignable state/action fields first and move the variable-length Pod id/name to the end.
- Example column order: marker/selection, status/action/role-or-kind, then Pod id/name.
- Long Pod identifiers should not break status/action alignment.
- Ticket rows and Pod rows may use different schemas, but each row family should align its own columns consistently.
- Improve Ticket/action row labels, status markers, and key hints.
- Improve detail pane content for selected Ticket/action rows:
- current phase;
@ -52,6 +60,9 @@ Refine the workspace panel layout, labels, ordering, and displayed detail so the
- `yoi panel` remains functional in both Ticket-enabled and no-Ticket workspaces.
- The primary row list makes user-action-required items visually distinguishable from passive background Pods.
- Ticket/action rows have aligned columns with the long Ticket title at the end, not the beginning.
- Pod rows have aligned columns with variable-length Pod id/name at the end, not the beginning.
- Short status/action fields stay visually comparable across rows.
- The active composer target is unambiguous.
- Common diagnostics are concise and actionable.
- Layout/display tests or snapshot-like unit tests cover key row/detail rendering decisions where practical.

17
.yoi/tickets/open/20260606-060548-workspace-panel-layout-display-tuning/thread.md
View File

@ -15,4 +15,21 @@ Created after closing the first-pass workspace orchestration panel implementatio
The first pass deliberately prioritized end-to-end behavior over visual/layout polish. This ticket owns the next tuning pass: row labels, key hints, detail pane content, composer target visibility, concise diagnostics, and optional phase/dependency/timeline display, while preserving existing TUI conventions and the thin ViewModel/action-dispatch boundaries.
---
<!-- event: decision author: hare at: 2026-06-06T08:36:49Z -->
## Decision
User layout direction:
Rows should be column-aligned instead of leading with long identifiers/titles.
- Ticket/action rows: move the long Ticket title to the end. Put short, alignable fields first, such as priority/action/status/phase/id-or-slug, then the title.
- Pod rows: move variable-length Pod id/name to the end. Put short, alignable fields first, such as status/action/role-or-kind, then the Pod id/name.
- Ticket and Pod rows do not need to share exactly the same schema, but each row family should keep stable aligned columns so status/action can be visually scanned.
This should be handled in the layout/display tuning ticket, not by changing backend/action semantics.
---