One MM button, tabbed window, and connection status in chat #1

Closed

erik wants to merge 0 commits from claude/mm-ui-one-window into main

erik commented

2026-09-26 13:56:37 +00:00

Owner

One button on the plugin bar, "MM", with the original icon.
One tabbed window: Main, Settings, Statistics, Mossy Tracker, Metas, Tools.
Mossy Tracker opens from its tab and has no bar button of its own.
Metas tab downloads metas and navs into the folder MossTank reads (vtank/mosstank/metas and navs).
The websocket's connecting / connected / error lines show in chat again, as in the original.

Backend messages are unchanged.

- One button on the plugin bar, "MM", with the original icon. - One tabbed window: Main, Settings, Statistics, Mossy Tracker, Metas, Tools. - Mossy Tracker opens from its tab and has no bar button of its own. - Metas tab downloads metas and navs into the folder MossTank reads (vtank/mosstank/metas and navs). - The websocket's connecting / connected / error lines show in chat again, as in the original. Backend messages are unchanged.

erik added 2 commits 2026-09-26 13:56:37 +00:00

One plugin-bar button and one tabbed window, as the original 336c5cfdf5

Live in 0.1.19 the plugin put three buttons on the plugin bar (MM, Mossy
Tracker, Metas), the tracker carried the icon that belongs to the main
window, and the metas downloads were in a window of their own.

Now only the main window has a bar button: "MM" with the original
window's icon (7735, 0x06001E37). Its tabs follow the original's notebook:
Main, Settings, Statistics, Mossy Tracker, Metas, Tools. The Mossy Tracker
tab is the original page, one "Open Mossy Tracker" button that opens the
tracker window; that window is registered without a bar button and
opened through the host's ShowPanel. The Metas tab holds everything the
metas window had (list with search, refresh, check, download outdated,
download one file, last check, status), plus the repository address and
the two folders the files land in. The main window forwards those
bindings to the meta sync's view model, since markup binds one object.

Downloads already went to the host's VTank profile storage, the one
MossTank reads, under mosstank/metas and mosstank/navs with each file's
own name and extension; the tab now shows those full folder paths
instead of the storage root. Backend frames are untouched.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Show the backend socket's status and errors in chat, as the original did 28794299cb

Live, /mm ws enable printed nothing about the connection: the socket's
connecting / CONNECTED / REGISTERED / error / reconnect / DISABLED lines went
only to the host log, which the windowed client does not show. The original
printed every one of them to chat.

BackendClient now queues each status and error line (original wording) and
still logs it; BackendSession drains the queue to chat on the tick, and right
after a start or stop on the tick thread so "[WebSocket] connecting…" and
"[WebSocket] DISABLED" come before the command's own reply, as in the
original. The socket thread never writes to chat. The original's telemetry-loop
and cleanup lines are emitted at the matching points, "Starting telemetry
loop" comes from the telemetry listener, and "Vital sharing re-subscribed" is
no longer verbose-only. No frame on the wire changes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>