Skip to content

Home button while editing + Actions folded into the profile pill (SDK 0.78.0) - #42

Merged
JamesmarkeyUK merged 2 commits into
mainfrom
claude/nav-profile-actions-combine-e2jj7t
Jul 27, 2026
Merged

Home button while editing + Actions folded into the profile pill (SDK 0.78.0)#42
JamesmarkeyUK merged 2 commits into
mainfrom
claude/nav-profile-actions-combine-e2jj7t

Conversation

@JamesmarkeyUK

Copy link
Copy Markdown
Contributor

Two changes to the editor's navbar, both gated on hasImages — the landing view is untouched.

The suite switcher becomes a home button

With an image open the identity keeps its logo and product name but loses the product dropdown, gaining a house glyph where the chevron was — the SDK's new onHome prop.

Universal PDF set the precedent: with a document open it drops the whole navbar and pins a home button into its dark toolbar, because switching products mid-edit is never what the logo is being clicked for. Images keeps its navbar, so it needed the prop rather than the same trick.

Wired to clearAll rather than following productHomeHref — navigating would reload the page and drop the open images anyway, and this brings the landing page straight back.

Actions and the profile become one control

AppMenu is now rows only — no trigger, no panel — passed to the new actions prop, so the editor bar reads home button on the left, one dropdown on the right, matching Universal Converter.

All three rows keep their behaviour: the hidden file input still drives "Open / Add images", Metadata keeps its two-line label and its ⚠ badge when the photo carries identifying data, and Clear all keeps its confirm and its count. Rows are inline-styled to the SDK dropdown's rhythm rather than Tailwind — they render inside SDK chrome now — and keep their per-row hover tints (green add, amber metadata, red destructive).

Notes

Lockfile bumped surgically (version, resolved, integrity, root range). A full npm install on this machine also strips the libc fields off rollup's optional platform packages — an artifact of an older npm here that would flip straight back on your next install. That matters more here than elsewhere because build-windows.yml runs npm ci; verified clean from an empty node_modules, and the app builds.

Checked by driving the built app in headless Chromium: switcher on the landing view, house glyph and merged pill once an image is loaded, all three rows present in the dropdown.

Requires @unisim/sdk 0.78.0, published from universal-platform#112.


Generated by Claude Code

claude added 2 commits July 27, 2026 07:34
With an image open the navbar identity keeps its logo and product name but
loses the product dropdown, gaining a house glyph where the chevron was —
the SDK's new `onHome` prop. Universal PDF set the precedent: with a
document open it drops the whole navbar and pins a home button into its
editor toolbar. Images keeps its navbar, so it needed the prop rather than
the same trick. The landing view is unchanged and still opens the switcher.

Wired to `clearAll` rather than following productHomeHref: navigating would
reload the page and drop the open images anyway, and this brings the
landing page straight back.

REQUIRES @unisim/sdk 0.78.0 on npm. package.json asks for ^0.78.0 while
package-lock.json still pins 0.77.1, so `npm ci` (build-windows.yml) will
refuse until someone runs `npm install` after the SDK publishes. Do not
merge before then.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015TVwu9Zr3bL9vQDfAcEroy
The home-button commit left the other half of the bar as it was: an
Actions button on the left and an avatar on the right, which is the split
the merged pill exists to remove. AppMenu is now rows only — no trigger,
no panel — passed to `actions`, so the editor bar reads home button on the
left, one dropdown on the right, matching Universal Converter.

All three rows keep their behaviour: the hidden file input still drives
"Open/Add images", Metadata keeps its two-line label and its ⚠ badge when
the photo carries identifying data, and Clear all keeps its confirm and
its count. Rows are inline-styled to the SDK dropdown's rhythm rather than
Tailwind — they render inside SDK chrome now — and keep their per-row
hover tints (green add, amber metadata, red destructive).

Still gated on `hasImages`, so the landing view is untouched: plain avatar,
suite switcher, no Actions.

Lockfile bumped surgically (version, resolved, integrity, root range) — a
full `npm install` here also strips `libc` off rollup's optional platform
packages, an artifact of this machine's older npm. `npm ci` verified clean
from an empty node_modules, and the app builds.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015TVwu9Zr3bL9vQDfAcEroy
@JamesmarkeyUK
JamesmarkeyUK merged commit 6d4dd97 into main Jul 27, 2026
1 of 2 checks passed
@JamesmarkeyUK
JamesmarkeyUK deleted the claude/nav-profile-actions-combine-e2jj7t branch July 27, 2026 11:31
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.

2 participants