The menu asks "What would you like to do?" and then grouped its rows by subject, which is not an answer to that. Mesh had grown to seven of the nineteen rows — live watching, passive browsing, and one transmit action in the same bucket — and Tools said nothing at all, since everything in the menu is a tool. So each section now names a doing, and holds what shares it: Message Chat · Channels · Courier · Contacts Watch Dashboard · Live feed · Watchtower · Time machine Explore Map · Mesh walk · Trace target · Trace path · Trophy case This node Device info · Device configuration · Device actions · Send advert Other nodes Repeater admin · TX optimize Four rows moved for a reason. Contacts is the address book the three features above it pick a recipient from, not a mesh view. Time machine is the past tense of the Dashboard, and was stranded in the grab-bag. Send advert is your own node announcing itself — a device action, filed with the mesh views only because it was about the mesh. And Repeater admin and TX optimize are the same job — someone else's radio, over the mesh, with credentials — which the old Device-management/Tools split hid. The two walks join the topology views they walk over, with the boards that score them underneath: see a node, walk to it, get scored. Nothing is renamed (a menu row still names the screen it opens) and no section is now larger than five rows or smaller than two. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
70 lines
2.3 KiB
Python
70 lines
2.3 KiB
Python
"""The ``timemachine`` tool: explore everything the recorder ever heard.
|
|
|
|
Opens the Time Machine (see :mod:`meshterm.ui.timemachine_screen`): pick the whole mesh
|
|
or any node ever observed and read its history as braille charts — reception volume,
|
|
the median-SNR band, the hour-of-day rhythm, packets and nodes per day, first-ever
|
|
arrivals — over a switchable 24 h / 7 d / 30 d / all-time window. The passive monitor
|
|
has been writing this history since the first session; this is where it pays off.
|
|
|
|
Menu-only: the explorer is interactive by nature (subjects, windows, scrolling); the
|
|
``monitor`` and ``nodes`` subcommands remain the scripted views over the same data.
|
|
"""
|
|
|
|
from __future__ import annotations
|
|
|
|
from typing import Any, Optional
|
|
|
|
import typer
|
|
|
|
from ..context import AppContext
|
|
from .base import Tool, ToolResult, register
|
|
|
|
|
|
@register
|
|
class TimeMachineTool(Tool):
|
|
"""Read the mesh's recorded past: per-node timelines, daily volumes, arrivals."""
|
|
|
|
name = "timemachine"
|
|
title = "Time machine"
|
|
icon = "⏳"
|
|
help = "Explore the recorded history — timelines, rhythms, arrivals"
|
|
category = "Watch"
|
|
order = 40 # the past tense of the Dashboard above it
|
|
|
|
async def prompt_params(self, ctx: AppContext) -> Optional[dict[str, Any]]:
|
|
"""Run the explorer; there are never parameters to collect.
|
|
|
|
The screen presents everything itself and returns when dismissed, so
|
|
returning ``None`` tells the menu the invocation is complete (the same
|
|
pattern as the ``dashboard`` tool).
|
|
|
|
Args:
|
|
ctx: Shared application context.
|
|
|
|
Returns:
|
|
Always ``None``.
|
|
"""
|
|
from ..ui.timemachine_screen import open_timemachine
|
|
|
|
await open_timemachine(ctx)
|
|
return None
|
|
|
|
async def run(self, ctx: AppContext, params: dict[str, Any]) -> ToolResult:
|
|
"""Nothing runs here: the Time Machine lives inside :meth:`prompt_params`.
|
|
|
|
Args:
|
|
ctx: Shared application context.
|
|
params: Unused.
|
|
|
|
Returns:
|
|
An empty :class:`ToolResult` (only reachable from a scripted call).
|
|
"""
|
|
return ToolResult(summary={})
|
|
|
|
def register_cli(self, app: typer.Typer) -> None:
|
|
"""Register no CLI command — the Time Machine is an interactive explorer.
|
|
|
|
Args:
|
|
app: The Typer application (untouched).
|
|
"""
|