Skip to content

Installer: switch between assistant and advanced view, fixed status and command dock - #250

Merged
ThomasPohl merged 1 commit into
mainfrom
feature/installer-view-switch
Nov 14, 2026
Merged

ThomasPohl merged 1 commit into
mainfrom
feature/installer-view-switch

Conversation

@ThomasPohl

Copy link
Copy Markdown
Owner

The installer page had the assistant on top and everything else in a <details> below it. "Advanced" meant scrolling a long page, and the hub's state and the action buttons scrolled out of view.

What changes

  • Two views instead of one long page. A bar at the top switches between Setup assistant and Advanced; each replaces the other. The view is part of the address (#wizard, #advanced/<tab>) and remembered in the browser. The bar also shows whether the hub is connected.
  • Advanced: status and commands stay in place. A dock (left; on top in a narrow window) holds the hub's state and last status (mode, schedule, next read and check-in, battery, SD card, firmware), all commands, the command line and the activity log. Firmware, settings, protocol view and console are tabs that scroll on their own; the console fills the window.
  • One Connect/Disconnect for the whole view (there were two connect buttons for the same port).
  • The status is read again after a scan; after a disconnect the last status stays visible, greyed.
  • Settings form in groups, with a save bar that stays in view; selects styled like inputs; "Show" button on password fields.
  • Command line: history on the arrow keys; reset, restart and send are disabled while not connected. The tools moved from their own section into the dock.
  • Assistant: finished steps can be opened from the progress bar; step 3 reuses a connection made in the advanced view; one banner for browsers without Web Serial.

No change to the serial commands or to what is sent to the hub, apart from the extra status after a scan.

Tested

Headless Chrome with a simulated hub (mocked Web Serial), 1400×850 and 420×800: view switch, address and reload, dock position while the tabs scroll, no page scroll in the advanced view, saving a setting, scan with the status refresh, command line and history, console, protocol replay, disconnect, assistant steps 1–4.

Not tested: a real hub, and the ESP Web Tools install buttons (blocked in the test environment; their markup is unchanged).


Generated by Claude Code

…nd command dock

The page had the assistant on top and everything else in a <details> below
it, so 'Advanced' meant scrolling a long page, and the hub's state and the
action buttons scrolled out of view.

- A bar at the top switches between the two views; the view is part of the
  address (#wizard, #advanced/<tab>) and remembered in the browser.
- Advanced: a dock with the hub's status (state, mode, schedule, battery, SD
  card, firmware), all commands, the command line and the activity log stays
  in place; firmware, settings, protocol view and console are tabs that
  scroll on their own. In a narrow window the dock sits on top.
- One Connect/Disconnect for the whole view instead of two connect buttons.
- The status is read again after a scan; the last status stays visible
  (greyed) after a disconnect.
- Settings form in groups with a save bar that stays in view; selects are
  styled like inputs; 'Show' button on password fields.
- Command line history on the arrow keys; reset, restart and send are
  disabled while not connected.
- Assistant: finished steps can be opened from the progress bar, step 3
  reuses a connection made in the advanced view, one banner for browsers
  without Web Serial.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Csa4N778M5kZxErLfAfd7D
@ThomasPohl
ThomasPohl merged commit 2f63243 into main Nov 14, 2026
26 checks passed
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