Skip to content

feat(pip): drop the header band, and let the platform name go before the logo - #193

Merged
jaywedgeworth22 merged 2 commits into
mainfrom
mm/pip-widget-layout
Oct 9, 2026
Merged

jaywedgeworth22 merged 2 commits into
mainfrom
mm/pip-widget-layout

Conversation

@jaywedgeworth22

Copy link
Copy Markdown
Collaborator

Board f324ec6, owner's PiP batch 2026-10-08.

The grey header is gone

The raised strip above the rows read as a stray silver tab. It's removed, and with it the app's own mark and the word "CodeCaps" — per the owner, once the header goes, the app's identity isn't wanted on the HUD at all. The provider logos identify it now.

The close/back control floats over the rows' top-right corner instead, still only while the pointer is over the window, so it never occupies permanent space above the numbers.

The name drops before the logo

This was the owner's conditional ask: "when the window is getting narrower, the first thing to go (after things have compressed as much as allowable) is the platform name ASSUMING WE FINALLY CAN MAKE THE LOGOS ACTUALLY SHOW UP."

Detail gained a logoOnly rung. The logo and the name used to disappear together at minimal, which left a row that was neither named nor identifiable. Now the name goes at logoOnly and the logo survives until minimal, where identity runs out entirely.

The condition is met: #190 ships the marks as colour/light/dark PNG triplets rather than SVGs, so they actually render.

Panel metrics follow — minHeight is one row plus padding, and the fit/visible-row maths no longer reserves a band that isn't there.

Verification

swift build clean; swift test 370 passed, 3 skipped, 0 failures, including a new testThePlatformNameDropsBeforeTheLogo that pins the order and the real width band that selects it.

Two tests that asserted the old header contract were updated rather than quietly dropped: the fit-height test no longer counts a header, and the header-text test went away with the header it described.

Not in this PR

Two of the five items are not here, and I want to be explicit rather than let the PR title imply otherwise:

  • Horizontal scroll below the squeeze point. The rows panel is still a vertical ScrollView; switching it needs a real width-driven scroll-axis decision and the owner asked for it at a specific point (~80–100pt wider than the squeeze point). Worth its own PR against this one.
  • The usage flame after the name or logo. This one may now be moot — the flame was to sit next to the platform name, and the app-name line it would have accompanied is the thing just removed. Worth confirming where the owner wants it before I put it somewhere they didn't ask for.

Both are tracked on f324ec6.

…the logo

Owner's PiP batch, 2026-10-08.  Board f324ec6.

The raised strip above the rows read as a stray silver tab.  It is gone, and
with it the app's own mark and the word "CodeCaps": the provider logos are
what identify a row now.  The close/back control floats over the rows'
top-right corner instead, still only while the pointer is over the window,
so it never occupies permanent space above the numbers.

The width ladder gained a `logoOnly` level.  The logo and the name used to
drop together at `minimal`, which left a nameless AND unidentifiable row;
the owner's instruction was that the name goes first and the logo stays, so
that is now its own rung between the named single-meter row and the
identity-free one.  His condition for this — "ASSUMING WE FINALLY CAN MAKE
THE LOGOS ACTUALLY SHOW UP" — is met by #190, which ships the marks as
colour/light/dark PNG triplets rather than SVGs.

Panel metrics follow the header's removal: `minHeight` is one row plus
padding, and the fit and visible-row maths no longer reserve a band.

Verified: swift build clean; swift test 370 passed / 3 skipped / 0 failures,
including a new testThePlatformNameDropsBeforeTheLogo that pins the order
and the real width band that selects it.  Two tests that asserted the old
header contract were updated rather than deleted silently: the fit-height
test no longer counts a header, and the header-text test is gone with the
header.
@kody-ai

kody-ai Bot commented Oct 9, 2026 •

Copy link
Copy Markdown

Code Review Completed! 🔥

The code review was successfully completed based on your current configurations.

Kody Guide: Usage and Configuration
Interacting with Kody
  • Request a Review: Ask Kody to review your PR manually by adding a comment with the @kody start-review command at the root of your PR.

  • Validate Business Logic: Ask Kody to validate your code against business rules by adding a comment with the @kody -v business-logic command.

  • Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Current Kody Configuration
Review Options

The following review options are enabled or disabled:

Options Enabled
Bug ✅
Performance ✅
Security ✅
Business Logic ✅

Access your configuration settings here.

​

@kody-ai

kody-ai Bot commented Oct 9, 2026

Copy link
Copy Markdown

kody code-review Kody Rules medium

Single-space sentence separation in the PR body violates the 2026-08-19 rule requiring two spaces between sentences in agent-written paragraphs. GitHub-flavored markdown collapses literal two ASCII spaces, so emit the literal HTML entity   after the period followed by a normal space (e.g., tab.  It's removed) to preserve the gap through the renderer.

Kody rule violation: Use two spaces between sentences in every human-facing string and agent-written paragraph

@kody-ai

kody-ai Bot commented Oct 9, 2026

Copy link
Copy Markdown

kody code-review Business Logic medium

🤔 Insufficient Task Context

I found a task linked to this PR, but it only contains minimal information (title only, no description or acceptance criteria). To perform a meaningful business rules validation, I need more details.

🔍 What I need to validate:

  • Business requirements and acceptance criteria
  • Expected behavior and business rules
  • Edge cases and constraints to consider

💡 How to improve the task context:

  • Add a description to the linked ticket
  • Include acceptance criteria or business rules
  • Describe the expected behavior after the change

⚠️ Important:

A task title alone is not sufficient to determine whether the implementation is correct or complete.


💡 This validation runs automatically only on the first review of a pull request. To run it again, comment @kody -v business-logic.

Comment thread Sources/CodeCaps/PipWidget.swift
…t row

Kody caught this on #193: the 18x18 close control sat flush in the panel's
top-trailing corner and overlapped the first row's right-edge percentage by
about 8x12pt.  controlInset existed for exactly this offset but nothing
consumed it, so the contract was declared and then not honoured.

Honours the constant rather than removing it, so the corner offset it was
designed for is now actually enforced.
@kody-ai

kody-ai Bot commented Oct 9, 2026 •

Copy link
Copy Markdown

Kody Review Complete

Great news! 🎉
No issues were found that match your current review configurations.

Keep up the excellent work! 🚀

⚠️ 4 Kody Rule(s) were not evaluated

These rules declare that they need repository context beyond this diff, and the review could not retrieve it, so they were not judged on this pull request:

  • Keep server secrets out of client bundles
  • Write the shared quota-windows.json only via LocalQuotaSnapshot.write
  • No manual screenshots or local UI previews; Mac UI via review + CI
  • Prefer Sentry for new observability; do not add new Datadog RUM/APM surfaces
Kody Guide: Usage and Configuration
Interacting with Kody
  • Request a Review: Ask Kody to review your PR manually by adding a comment with the @kody start-review command at the root of your PR.

  • Validate Business Logic: Ask Kody to validate your code against business rules by adding a comment with the @kody -v business-logic command.

  • Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Current Kody Configuration
Review Options

The following review options are enabled or disabled:

Options Enabled
Bug ✅
Performance ✅
Security ✅
Business Logic ✅

Access your configuration settings here.

​

@jaywedgeworth22
jaywedgeworth22 merged commit b74622b into main Oct 9, 2026
2 checks passed
@jaywedgeworth22
jaywedgeworth22 deleted the mm/pip-widget-layout branch October 9, 2026 00:49
@kody-ai

kody-ai Bot commented Oct 9, 2026

Copy link
Copy Markdown

kody code-review Business Logic medium

🤔 Insufficient Task Context

I found a task linked to this PR, but it only contains minimal information (title only, no description or acceptance criteria). To perform a meaningful business rules validation, I need more details.

🔍 What I need to validate:

  • Business requirements and acceptance criteria
  • Expected behavior and business rules
  • Edge cases and constraints to consider

💡 How to improve the task context:

  • Add a description to the linked ticket
  • Include acceptance criteria or business rules
  • Describe the expected behavior after the change

⚠️ Important:

A task title alone is not sufficient to determine whether the implementation is correct or complete.


💡 This validation runs automatically only on the first review of a pull request. To run it again, comment @kody -v business-logic.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant