Main menu: Device config, Support MeshTerm

Two rows renamed, and the rename carried into the screens they open —
the config editor's table title and its staged-count header, the support
page's own title (it comes from the tool, so it followed on its own).

"Support this project" never said which project; the menu is MeshTerm's
and the section above it is already About MeshTerm, so the name is the
useful half of that phrase. "Device configuration" was the longest label
in the list and set the width of the whole name column: at 19 cells
instead of 23, every description now gets 51 and the widest row is 68.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Jean-Pierre MartineauandClaude Opus 5 committed 2026-08-12 17:15:00 -04:00
1 parent 1693367f41
commit ea9b7c1cb1
7 files changed
+11 -11

No files matched your search

+1 -1
View File
@@ -126,7 +126,7 @@ here with its scripted equivalent, where one exists.
| Feature | What it does | Scripted |
| --- | --- | --- |
| **📋 Device info** | The connected companion's identity and full radio configuration at a glance. | `meshterm info` |
| **🔧 Device configuration** | View and *stage* changes to every setting (name, radio, behaviour, experimental) for review before applying, with TOML backup/restore. | `meshterm config` / `config set <key> <value>` |
| **🔧 Device config** | View and *stage* changes to every setting (name, radio, behaviour, experimental) for review before applying, with TOML backup/restore. | `meshterm config` / `config set <key> <value>` |
| **🔨 Device actions** | Immediate operations on the box itself: clock sync, TOML backup/restore, the identity key, reboot, and factory reset — each acting the moment it's confirmed, with destructive ops gated. | `config backup` / `restore` / `reboot` / … |
| **📡 Send advert** | Announce this node to the mesh — a zero-hop or flood advertisement, or share this node's contact card as a QR code. | `meshterm config advert` / `config share` |
| **🔌 Device discovery** | Enumerate serial *and* Bluetooth LE companions, pick one interactively (or auto-select the only one present), add a network (TCP) companion by host:port, and remember the last good default. A dropped link is detected live and offers to reconnect. | `meshterm devices` |
+3 -3
View File
@@ -1,6 +1,6 @@
"""The About MeshTerm tools: the three pages under the menu's last section.
*About MeshTerm*, *About the author*, *Support this project* — in that order, which is
*About MeshTerm*, *About the author*, *Support MeshTerm* — in that order, which is
the order a stranger asks the questions in: what is this, who made it, how do I help.
Each is a page rather than a feature: it reads nothing, transmits nothing, and needs no
device, so it opens straight to its screen (see :mod:`meshterm.ui.about`) instead of
@@ -118,14 +118,14 @@ class SupportProjectTool(_AboutTool):
"""What keeps MeshTerm going, and the ways — paid and unpaid — to help it along."""
name = "support"
title = "Support this project"
title = "Support MeshTerm"
icon = "💰"
help = "What keeps MeshTerm going, and how to help"
order = 30 # the ask, and only once the first two have earned it
@staticmethod
def page() -> "MarkdownDoc":
"""The *Support this project* page."""
"""The *Support MeshTerm* page."""
from ..ui.about import support_project
return support_project()
+1 -1
View File
@@ -35,7 +35,7 @@ class ConfigTool(Tool):
"""View and edit the connected device's full configuration."""
name = "config"
title = "Device configuration"
title = "Device config"
icon = "🔧"
help = "Device settings — identity, radio, tuning, …"
category = "This node"
+1 -1
View File
@@ -73,7 +73,7 @@ def about_author() -> MarkdownDoc:
def support_project() -> MarkdownDoc:
"""The *Support this project* page: what keeps it going, and how to chip in.
"""The *Support MeshTerm* page: what keeps it going, and how to chip in.
Deliberately two-sided — money is one way to help and not the only one, so the page
keeps a section for the other kind rather than folding it into a donate link.
+3 -3
View File
@@ -2,7 +2,7 @@
Two sibling screens live here, deliberately kept distinct:
* **Device configuration** (:func:`edit_config`, behind the ``config`` tool) — one grouped,
* **Device config** (:func:`edit_config`, behind the ``config`` tool) — one grouped,
column-aligned list of every setting under its category heading, each row showing its
current value, any staged change, and a one-line explanation. Editing a row *stages* the
new value (shown as ``current → new``) and nothing touches the radio until *Apply*;
@@ -223,7 +223,7 @@ def config_table(
# Match the contacts list: a frameless SIMPLE_HEAD table with a left-justified accent title
# and muted headers, so the two screens read as one family (see widgets.contacts_table).
table = Table(
title="[accent]Device configuration[/accent]",
title="[accent]Device config[/accent]",
title_justify="left",
box=box.SIMPLE_HEAD,
show_edge=False,
@@ -383,7 +383,7 @@ def _menu_items(
# Back spells out the consequence of leaving (see menus.exit_rows).
items.extend(exit_rows(staged, apply_value=_APPLY, back_value=_CANCEL))
title = "Device configuration" + (f" — {staged} staged" if staged else "")
title = "Device config" + (f" — {staged} staged" if staged else "")
return title, items
+1 -1
View File
@@ -86,7 +86,7 @@ def test_unwritten_sections_speak_the_empty_state_voice(builder) -> None: # noq
def test_prose_wraps_into_its_own_indented_block() -> None:
"""A wrapped placeholder hangs under its heading rather than falling to column 0."""
screen = AboutPage("Support this project", support_project())
screen = AboutPage("Support MeshTerm", support_project())
screen.note_viewport(40)
# Narrow enough to force every placeholder to wrap at least once.
lines = plain(screen.render_body(28)).splitlines()
+1 -1
View File
@@ -406,7 +406,7 @@ def _about_author(cols: int, rows: int) -> Screen:
def _support_project(cols: int, rows: int) -> Screen:
return AboutPage("Support this project", support_project())
return AboutPage("Support MeshTerm", support_project())
_ENTRIES: list[_Entry] = [