Repository navigation
feat(ui): widen the home and chat canvases and cap answers at 88ch - #189
Merged
Merged
Conversation
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
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.
What does this PR do?
Separates the workspace width from the long-form reading measure: the home page
and the chat canvas get a wider (~1024px) layout, while an answer and the note
editor keep a comfortable line length.
Why?
Three caps used to stack, and the effect was nearly an illusion of width:
max-w-3xl(~768px), too narrow for alg:grid-cols-3notebook shelf,
--reading-measure(72ch, ~600px), andmax-w-[85%]on top, so body text was really72ch × 85% ≈ 61chwhile the composer spanned the whole centre panel.Desktop chat is a workspace, not an article column, so the two widths are now
separate concepts: page width and optimal body line width.
Related issue
Standalone UI change; no issue.
What changed?
Home.tsx): both shellsmax-w-3xl → max-w-5xl(~768px → ~1024px),so search, the three-column notebook shelf and recent content use the space.
MessageList.tsx): the header, empty state and message listmax-w-[var(--reading-measure)] → max-w-5xl.MessageItem.tsx):max-w-[85%] → w-full max-w-[var(--answer-measure)].No second compression; an answer is still capped, just at 88ch instead of
72ch × 85%.max-w-[85%]; short messages stay a small bubblebecause the inner bubble is
w-fit.ProcessPanel.tsx): centred on the samemax-w-5xlcanvas, sothe input lines up with the transcript it answers.
theme.css):--answer-measure: 88chadded;--reading-measurestays 72ch and now belongs to the note editor.
claiming chat and notes share one.
Note editor is unchanged: still
--reading-measure(72ch).How was this tested?
Verifyis green on Linux, macOS and Windows — typecheck, design guard,unit tests,
electron-builder --dir, andsmoke:packaged.npm test— 478 pass.npx electron-vite build— bundles.npm run check:design— no violations (--answer-measureis a token, not ahard-coded
ch).npx eslinton the touched files — no errors.Screenshots / recordings
Not attached: this environment has no display to capture the Electron window.
The change is layout-only; the diagram above is the intended geometry. A visual
pass on a real window is welcome before merge.
Checklist
npm run typecheckpasses (CI).npm run buildpasses (CI).Desktop / build changes