feat(tui): add splitlayout for shared two-pane geometry and borders - #86
Merged
Merged
Conversation
roborev: Combined Review (
|
This was referenced Sep 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Roborev and kata each implement the same split-screen sizing — a clamped list pane beside a detail pane with matching 140x36 breakpoints and border-box frames.
tui/splitlayoutextracts it so both can delete their copies and vet's TUI starts on the shared implementation.Configcarries each application's constants (list-width clamps, detail pane reserved width, body-height floor).Geometrycomputes border-box outer and inner pane rectangles from the terminal size and footer height with no hidden clamping, so undersized calls keep each project's current results, including roborev's negative detail widths.PickLayoutowns the shared breakpoints;PaneStylewraps content in the standard border with a caller-resolved color.Layout locking, focus dispatch, and content rendering stay with each application. Output matches the existing implementations byte for byte across the sizing grid and both focus states.
The consumer migrations follow as separate PRs, independent of #85. Whichever of that one and this one merges first rebases the other.
Refs kenn-io/kennel#132 (vet roadmap slice 9)