Skip to content

gui: Let the home window choose its height - #78

Open
BenWestgate wants to merge 2 commits into
codex/gui-tails-field-testfrom
codex/gui-natural-home-height
Open

BenWestgate wants to merge 2 commits into
codex/gui-tails-field-testfrom
codex/gui-natural-home-height

Conversation

@BenWestgate

@BenWestgate BenWestgate commented Sep 30, 2026 •

Copy link
Copy Markdown
Owner

Closes #75.

Remove the fixed 620px default window height, retain its 880px width, and let only the six-action home page propagate its natural scroller height. Other workflow pages keep their scrolling behavior. This follows GTK4's size-request behavior without a release-specific height.

b347792 fixes the current-head review finding: the home scroller previously did not propagate its content height, so simply removing the default left the initial window undersized. The change affects two GUI files; no wallet or recovery behavior changes.

Validation: 71 GUI tests, Ruff lint/format, bytecode compilation, and git diff --check passed. Supported-Tails minimum-resolution sizing and long-page scrolling remain manual release gates.

AI assistance was used for these authorized changes. Human review remains required.

@chatgpt-codex-connector

This comment has been minimized.

@BenWestgate BenWestgate added gui Graphical user interface behavior. gate: adversarial review Resolve, merge, or explicitly defer before the next full adversarial review. labels Sep 30, 2026 — with ChatGPT Codex Connector

@BenWestgate BenWestgate left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AI-generated release-gate review, posted at the maintainer's request.

Code ACK d510621.

The diff removes only the fixed default_height=620; the 880px default width, navigation, page content, and scrolling hierarchy are unchanged. GTK4 documents that an unset default dimension uses the window's natural size request, while the window remains resizable. Every workflow page is still hosted by the existing Gtk.ScrolledWindow, so longer pages remain usable at the smaller initial home height.

Manual qualification remains appropriate: verify the home opens compactly and a representative long page scrolls at the supported Tails guest resolution. No further automated Codex review request is warranted for this one-line behavior change.

@BenWestgate BenWestgate left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated release-gate review for rebased head 7b82ebc.

Code ACK. The PR is again exactly one commit / one file / one behavioral change on top of current #77: remove default_height=620 while retaining default_width=880. The prior review rationale is unchanged. Manual Tails confirmation of compact home height plus scrolling on a representative long page remains the only qualification item.

@BenWestgate
BenWestgate force-pushed the codex/gui-natural-home-height branch from 7b82ebc to 38373b3 Compare September 30, 2026 02:21

@BenWestgate BenWestgate left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated release-gate review for rebased head 38373b3.

Code ACK. The PR remains exactly one commit / one file / one behavioral change on top of current #77: remove default_height=620 while retaining default_width=880. Manual Tails confirmation of compact home height plus scrolling on a representative long page remains the only qualification item.

Copy link
Copy Markdown
Owner Author

Agent release-gate review at exact head 38373b3: this is a one-line behavioral layout change—leave width at 880 and omit the forced 620px height so GTK/libadwaita can use the home page's natural height. Long workflow pages still use the existing scrolled container. Exact-head run 36659468950 succeeded. No code-review blocker found; the initial home size and long-page scrolling still need the planned manual Tails guest-resolution check before the GUI candidate is frozen.

@BenWestgate BenWestgate left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AI-generated review (Codex), posted at the maintainer's request.

ACK 38373b3. Removing the forced window height is safe.

@BenWestgate BenWestgate left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Codex current-head review at 38373b3: no findings. Removing the fixed default height lets the existing navigation content determine window height.

BenWestgate added a commit that referenced this pull request Oct 20, 2026
Restore the Codex32 Book checksum worksheet command removed in 1a14000,
following BlockstreamResearch/codex32 discussion #78: checksum
generation is acceptable when it is clearly separate from validation
and correction and is never used on completed shares.

Compared with the removed command:
- it accepts only the Book checksum worksheet's 32 squares; input of
  any complete ms string length is refused with a pointer to check, so
  a damaged complete string can no longer be checksummed as a longer
  unchecksummed payload;
- the warning also forbids replacing the checksum of an existing
  backup, and help text names check and correct for existing backups;
- it stays ms32-only, interactive-only, needs two matching entries
  with the screen cleared between them, and gives no format hints.

The library keeps no public completion API; the command builds the
string with the existing private _from_parts.

Claude-Session: https://claude.ai/code/session_01C8Ur3dhqpcWU3gEYsweXNM
BenWestgate added a commit that referenced this pull request Oct 21, 2026
Restore ms32 checksum, removed in 1a14000, as a generation-only command
separate from check and correct, following codex32 discussion #78.

The command accepts only the Codex32 Book checksum worksheet's 32
non-pink squares after the ms prefix and refuses every complete ms
string length, so a damaged complete string cannot be mistaken for a
longer unchecksummed payload. It requires an interactive terminal,
warns against re-checksumming an existing backup or entering raw dice,
seed words, hex seeds or passwords, and gives no format hints.

The non-pink squares are entered twice with the screen cleared between
entries. The completed string is then shown, the checksum is copied
into the pink squares, and after another clear only those 13 squares
are typed back. Only then does the string reach stdout. Every entry
must be single-case ASCII; --plain keeps the input case.

Security: checksum generation for new data. The repeated entries catch
typing errors but not errors already on the worksheet, and nothing can
prove the data was generated well; the warning and docs say so.

Validation: ruff, ruff format, mypy, python -m pytest -q and
python -O -m pytest -q.

Claude-Session: https://claude.ai/code/session_01C8Ur3dhqpcWU3gEYsweXNM
BenWestgate added a commit that referenced this pull request Oct 22, 2026
Restore ms32 checksum, removed in 1a14000, as a generation-only command
separate from check and correct, following codex32 discussion #78.

The command accepts only the Codex32 Book checksum worksheet's 32
non-pink squares after the ms prefix and refuses every complete ms
string length. This narrows, but cannot remove, the chance that a
damaged existing backup is taken for new unchecksummed data: one that
lost or gained characters can still reach the accepted length. It
requires an interactive terminal, warns against re-checksumming an
existing backup or entering raw dice, seed words, hex seeds or
passwords, and gives no format hints.

The non-pink squares are entered twice with the screen cleared between
entries. The completed string is then shown, the checksum is copied
into the pink squares, and after another clear only those 13 squares
are typed back. Only then does the string reach stdout. Every entry
must be single-case ASCII; --plain keeps the input case.

Security: checksum generation for new data. The repeated entries catch
typing errors but not errors already on the worksheet, and nothing can
prove the data was generated well; the warning and docs say so.

Validation: ruff, ruff format, mypy, python -m pytest -q and
python -O -m pytest -q.

Claude-Session: https://claude.ai/code/session_01C8Ur3dhqpcWU3gEYsweXNM
@BenWestgate

Copy link
Copy Markdown
Owner Author

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-24T09:09:03.666928Z b347792 Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 38373b39b4

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/codex32_gui/app.py
@BenWestgate

Copy link
Copy Markdown
Owner Author

Is this PR really necessary? What problem is it trying to solve?

Let the home page scroller contribute its natural height to the initial window size. Other workflow pages still scroll without requesting their full height. refs #75

Copy link
Copy Markdown
Owner Author

Yes—#75 records the Tails home-window sizing defect. The reviewer was right: removing default_height alone left the home scroller at its minimum height. Fixed in b347792: only the home page propagates natural height, with no new pixel constant. 71 GUI tests and Ruff pass; Tails visual qualification remains.

Copy link
Copy Markdown
Owner Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Swish!

Reviewed commit: b347792ea6

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gate: adversarial review Resolve, merge, or explicitly defer before the next full adversarial review. gui Graphical user interface behavior.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant