Scope means only what MeshCore means by it
The menu's This node / Other nodes / This app sections were called scopes; they now name whose a setting is, and scope is left to a flood's region alone. CLAUDE.md's lexicon says so. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
326f6f5479
commit
2976bf9e08
6 files changed
+8
-8
No files matched your search
@@ -65,7 +65,7 @@ them instead of hand-rolling:
|
||||
| route | the concrete node sequence a trace walked or will walk |
|
||||
| via | prefix for a packet/message's relay chain |
|
||||
| region | a named area a repeater relays floods for (`region put yul`); shown bare, never `#yul` — the `#` belongs to key derivation only |
|
||||
| scope | the region a flood is limited to — a packet's, a channel's send scope, the device's default scope. A direct packet has none |
|
||||
| scope | the region a flood is limited to — a packet's, a channel's send scope, the device's default scope. A direct packet has none. MeshCore's sense and the only one: the menu's This node / Other nodes / This app sections name *whose* a setting is, never a "scope" |
|
||||
| unscoped | a plain flood, relayed by any repeater that allows the wildcard `*` |
|
||||
| Back | leave the current screen/list — Esc's word, and a row's only where leaving is a *choice* (see below) |
|
||||
| Quit | leave the app (main menu, device splash) — nowhere else |
|
||||
|
||||
@@ -242,7 +242,7 @@ want the node on the mesh all the time. The device-side scripts both manuals run
|
||||
The menu asks one question — *what would you like to do?* — and answers it in two halves.
|
||||
Three sections name a doing: **Message** is chat, channels, the courier outbox and
|
||||
contacts; **Watch** is the dashboard, the live feed, the watchtower and the time machine;
|
||||
**Explore** is the map, the mesh walk, tracing and the trophy case. Three name a scope:
|
||||
**Explore** is the map, the mesh walk, tracing and the trophy case. Three name whose it is:
|
||||
**This node** is the radio in your hand, **Other nodes** is someone else's over the mesh,
|
||||
and **This app** is MeshTerm itself — preferences, diagnostics, and the written pages.
|
||||
|
||||
|
||||
+2
-2
@@ -5,7 +5,7 @@ the catalogue; [the command line](cli.md) is the manual for the scripted half of
|
||||
|
||||
MeshTerm's menu asks one question — *what would you like to do?* — and its six sections
|
||||
answer it in two halves. The first three name a **doing**: Message, Watch, Explore. The
|
||||
last three name the **scope** a setting belongs to: This node, the radio in your hand;
|
||||
last three name **whose** a setting is: This node, the radio in your hand;
|
||||
Other nodes, someone else's over the mesh; and This app, the program in front of you.
|
||||
|
||||
Every interactive screen is listed here with its scripted equivalent, where one exists.
|
||||
@@ -58,7 +58,7 @@ Every interactive screen is listed here with its scripted equivalent, where one
|
||||
|
||||
## ⚙ This app — the program in front of you
|
||||
|
||||
The last scope, and the one nothing on the mesh can answer. Preferences leads it because
|
||||
The last of the three, and the one nothing on the mesh can answer. Preferences leads it because
|
||||
it is the only row here that *changes* MeshTerm rather than describing it; the written
|
||||
pages close it.
|
||||
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
*About MeshTerm*, *About the author*, *Join Discord*, *Support MeshTerm* — in that
|
||||
order, which is the order a stranger asks the questions in: what is this, who made it,
|
||||
where is everyone, how do I help. They share the *This app* section with Preferences,
|
||||
which leads it: the section is the app's own scope, and the one row that *changes*
|
||||
which leads it: the section is the app's own, and the one row that *changes*
|
||||
MeshTerm sits above the four that describe it.
|
||||
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
|
||||
|
||||
@@ -202,10 +202,10 @@ _REGISTRY: dict[str, Tool] = {}
|
||||
#: everything that shares it. Message leads (the everyday features, plus the book you
|
||||
#: pick a recipient from), then Watch (what the mesh is doing, what it did, what to be
|
||||
#: told about), Explore (where the nodes are, how they reach each other, and the boards
|
||||
#: that score the walking), then the two scopes a setting can belong to — This node, the
|
||||
#: that score the walking), then the two owners a setting can belong to — This node, the
|
||||
#: radio in your hand, and Other nodes, someone else's over the mesh.
|
||||
#:
|
||||
#: This app closes the list as the third and last *scope*, after the radio in your hand and
|
||||
#: This app closes the list as the third and last *owner*, after the radio in your hand and
|
||||
#: someone else's over the mesh: the program in front of you. It holds the one thing that
|
||||
#: changes how MeshTerm behaves (Preferences) and the four pages that say what MeshTerm is
|
||||
#: — questions none of the doings above can hold, and which nothing on the mesh can answer.
|
||||
|
||||
@@ -12,7 +12,7 @@ staging eleven changes or from a single ``preferences set``.
|
||||
|
||||
This is deliberately the *app's* tool, not the radio's. It reads nothing from the
|
||||
companion, transmits nothing, and works with no device attached at all — which is why it
|
||||
leads the **This app** section (the third scope, after this node and other nodes) rather
|
||||
leads the **This app** section (the third owner, after this node and other nodes) rather
|
||||
than sitting beside Device config.
|
||||
"""
|
||||
|
||||
|
||||
Reference in new issue
Block a user