oss/Portal
1
0
Fork 0
Code Issues 1 Pull requests 1 Projects Releases 1 Packages Wiki Activity

Connect in the browser layout instead of the connect screen #19

Merged
oss merged 3 commits from fix/connect-in-main-ui into main 2026-11-06 00:20:14 +01:00
Conversation 0 Commits 3 Files changed 11 +276 -30
oss commented 2026-11-05 20:06:28 +01:00
Owner
Copy link

At startup with a remembered server (Reconnect on launch, or a server on the command line), Portal showed the connect screen, with every server card and the add-server form, while it reconnected. It now opens in the browser layout and connects there.

What changes

  • New connecting screen (ConnectingView, ConnectingViewModel). It uses the browser's frame: command bar, sidebar with the saved servers and Add server, and the status bar saying "Connecting to Tower…". The server pane shows the connect steps and Cancel.
  • When it's used: every connect that doesn't start from a card on the connect screen. That covers startup, a server in the sidebar, and Ctrl+K. Connect on a card still shows progress on that card.
  • Startup: MainViewModel.PrepareStart picks the server and sets the screen before the window is shown, so the connect screen never shows for a frame.
  • Failure: the screen stays, with the error, Try again and Edit server. The status dot turns red ("Not connected to Tower").
  • Cancel or a declined prompt: returns to the open connection, or to the connect screen when there is none. Picking another server in the sidebar cancels the current attempt first.
  • The connect step template moved from ConnectView.xaml into Themes/Styles.xaml, so both screens share it.
  • DESIGN.md: a state entry and a change entry.

Verification

  • dotnet build: 0 warnings, 0 errors.
  • dotnet test Portal.slnx: 171 passed, 17 skipped, 0 failed.
  • Portal.Shots: new scenes 16-startup-connecting and 17-startup-connect-error in both themes. I looked at them, and also at 02-connect-progress-error to check the shared step template.
  • Not covered: a real startup in a live window. The shots render the screen; they don't run the startup path.

Kaneo: Wait in the normal UI while connecting at start (POR-6).

🤖 Generated with Claude Code

At startup with a remembered server (Reconnect on launch, or a server on the command line), Portal showed the connect screen, with every server card and the add-server form, while it reconnected. It now opens in the browser layout and connects there. ## What changes - **New connecting screen** (`ConnectingView`, `ConnectingViewModel`). It uses the browser's frame: command bar, sidebar with the saved servers and Add server, and the status bar saying "Connecting to Tower…". The server pane shows the connect steps and Cancel. - **When it's used:** every connect that doesn't start from a card on the connect screen. That covers startup, a server in the sidebar, and Ctrl+K. Connect on a card still shows progress on that card. - **Startup:** `MainViewModel.PrepareStart` picks the server and sets the screen before the window is shown, so the connect screen never shows for a frame. - **Failure:** the screen stays, with the error, Try again and Edit server. The status dot turns red ("Not connected to Tower"). - **Cancel or a declined prompt:** returns to the open connection, or to the connect screen when there is none. Picking another server in the sidebar cancels the current attempt first. - The connect step template moved from `ConnectView.xaml` into `Themes/Styles.xaml`, so both screens share it. - DESIGN.md: a state entry and a change entry. ## Verification - `dotnet build`: 0 warnings, 0 errors. - `dotnet test Portal.slnx`: 171 passed, 17 skipped, 0 failed. - Portal.Shots: new scenes `16-startup-connecting` and `17-startup-connect-error` in both themes. I looked at them, and also at `02-connect-progress-error` to check the shared step template. - Not covered: a real startup in a live window. The shots render the screen; they don't run the startup path. Kaneo: *Wait in the normal UI while connecting at start* (POR-6). 🤖 Generated with [Claude Code](https://claude.com/claude-code) 
At startup with a remembered server, Portal showed the connect screen
with every server card and the add-server form while it reconnected.
Connects started outside the connect screen (startup, the sidebar,
Ctrl+K) now show the browser layout with the steps in the server pane.
A failure stays there with Try again and Edit server; Cancel returns to
the open connection or the connect screen.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Switching from A to B and back to A before the first A attempt finished
cancelling let that attempt reset the card and navigate away from the
new connecting screen. Cleanup now runs only for the card's current
attempt and only leaves the screen that attempt created.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
oss merged commit 02c48f9882 into main 2026-11-06 00:20:14 +01:00
oss deleted branch fix/connect-in-main-ui 2026-11-06 00:20:14 +01:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
oss/Portal!19
No description provided.