@yuneta/gobj-ui 7.23.140 → 7.23.142

package/README.md

@@ -221,7 +221,11 @@ seen*:
   Off by default: a tree whose children are pages wants the item to BE the
   destination. On for a tree whose children are workspaces with a position
   inside them — the agent console's strip of treedbs, each with its open topic.
-  Since 6.2.0.
+  Since 6.2.0. **Declarable in a child spec since 7.23.140** (`"remember_position":
+  true` next to its `id`): the attr existed, but the spec never passed it on,
+  so a node declared in a config could not turn it on. yunovatios turns it on
+  for its treedb nodes, so the graph tab returns to `<graph>/<topic>` with its
+  focus and the data tab to the topic that was open.
 
 - **`nav_mode` — the three shapes as one runtime knob.** The two bullets above
   describe what a tree *declares*; `nav_mode` is how a user *chooses* between
@@ -1290,8 +1294,8 @@ a level or two, with a count on every cut.
   parent shows it or it is a shown root — the **union**, so a device that hangs
   from its place AND its controller is drawn once, under whichever opened
   first, and folding one of the two leaves it where the other shows it.
-- **`expand_depth`** (default `2`) is how much opens on load: the roots and
-  their children. **`fold_page_size`** (default `24`) is how many children of
+- **`expand_depth`** (default `1` since `7.23.142`, `2` before) is how much
+  opens on load until the reader steps: the roots alone. **`fold_page_size`** (default `24`) is how many children of
   one hook are shown at a time; the rest is a **`+N` chip** at the end of the
   page that opens the next one. Both are attrs of `C_YUI_TREEDB_GRAPH`,
   forwarded to the engine — and since `7.23.93` so are the seven the engine
@@ -1310,15 +1314,28 @@ a level or two, with a count on every cut.
   the container in the capture phase over four event types, exactly as the
   JSON graph's fold handles are — G6 never reads the DOM `click`, it builds its
   own from the pointer pair.
-- **The toolbar's fold pair** (the same two chevrons as the JSON graph):
-  *expand all* opens every hook on all its children — the reader asking for
-  the pile on purpose — and *collapse all* leaves the roots. *Refresh* is the
-  way back to the default depth. **Neither moves the zoom** (since `7.23.78`):
-  a fold is not a reason to change the scale the reader chose, and until then
-  both fitted the whole graph — opening everything zoomed out to a strip and
-  closing it zoomed in on the roots, every time. The camera holds the anchor
-  still when there is one, else the first root: the top of the tree, which is
-  where a JSON viewer keeps the eye when it opens or closes everything.
+- **The toolbar's fold STEPPER** (since `7.23.141`; it replaced the *expand
+  all* / *collapse all* pair): `▸` · **`places level 2/4`** · `▾`. It walks the
+  **main tree** one level at a time, the way the frontend view opens one level
+  per press: level 1 is the main topic's roots (and the loose records the
+  reader asked to see), each `▾` opens the next level through every topic that
+  is not hidden, each `▸` folds the deepest one. The readout says what the two
+  buttons act on — the main topic's swatch and name (data, never translated;
+  gone on a phone, the numbers stay) and `level N/M` — the WORD as well as the
+  numbers, because the legend chip under it says `places 2/4` too and there it
+  means records on screen — and a button is disabled at either end. **A level is a floor, not a picture**: stepping down
+  opens only what is folded above the new level and keeps the pages and pills
+  already open; stepping up folds from the new level down and touches nothing
+  above it. A topic the schema does not tie to the main one is a tree of its
+  own, has no level, and is opened by its pills. The level is the reader's,
+  per treedb: `fold_level` is `SDF_PERSIST` on `C_YUI_TREEDB_GRAPH`, handed to
+  the engine on creation (`0` = never stepped = `expand_depth`), so a reload
+  or a *refresh* opens where it was left. The old pair opened every hook of the
+  treedb at once — the pile, on purpose, which on a treedb of thousands nobody
+  reads — and closing threw away everything the reader had opened.
+  **It does not move the zoom** (since `7.23.78`): a fold is not a reason to
+  change the scale the reader chose. The camera holds the anchor still when
+  there is one, else the first root.
 - **`dagre` reads LEFT TO RIGHT** now, with explicit `nodesep`/`ranksep`: the
   children of a node are a column beside it and the graph reads like a file
   tree. The ports move to the sides with it (fkeys on the left edge, hooks
@@ -1424,9 +1441,11 @@ screen every card is a smudge. Since `7.23.82` a record has **three views**
   still be drawn. The same one-line chip a leaf record already is, at the
   tier's width (200 / 180 / 160 px). No pills.
 - **`shape`** — a **figure** of the topic's colour, no ports, no text: the
-  topology and nothing else. A native G6 node — square (rounded `rect`),
-  circle, diamond, triangle, hexagon or star — so the focus, the selection
-  and the anchor are its own stroke and halo. The three tiers keep their
+  topology and nothing else. A native G6 node — a **circle** by default
+  (since `7.23.133`; a square until then), or a square (rounded `rect`),
+  diamond, triangle, hexagon or star — in the outline the card and the pill
+  wear (1, or the width chosen; it was a floor of 2) — so the focus, the
+  selection and the anchor are its own stroke and halo. The three tiers keep their
   order of size (32 / 28 / 22), the structural tier its dashed border. The
   figure is chosen in the **node properties** popover (`shape`, with the
   popover's own scope: this node, the topic, every node), remembered as the
@@ -1442,9 +1461,12 @@ UNDER the html: the first repaint (a selection, the focus, a theme switch, a
 pill appearing) rebuilt that html from the topic's colour and the choice was
 gone, and nothing of it ever reached the store. Choosing the topic's own
 colour back, with the stroke and line width that go with it, **forgets** the
-entry instead of writing it: the palette is assigned by position, so a
-colour written down would freeze today's palette on that card — the trap the
-sizes fell into in `7.23.80`.
+entry instead of writing it: the palette is assigned by the topics'
+ALPHABETICAL order (since `7.23.136`, in the graph and the schema diagram
+alike; by the backend's order before, which varies from load to load, so two
+topics could swap colours), and adding a topic still shifts it — a colour
+written down would freeze today's palette on that card, the trap the sizes
+fell into in `7.23.80`.
 
 In the view's toolbar (`C_YUI_TREEDB_GRAPH`), next to the fold pair: three
 push buttons in one group — a card, a line, a figure — the pressed one being
@@ -1478,12 +1500,59 @@ the day into the treedb, and a later default (the bigger ports above) reached
 no saved treedb: the same trap as the invented cascade coordinates, for the
 size. A card on its tier's default now saves its position and nothing else;
 a closed node saves no size at all (a square is not the card's size), its
-entry keeps what it had. And the node's context menu, in edition, has the way
-back: **reset sizes** / **reset topic sizes** forget every saved size, port
-radius and per-port radius — per node and as topic defaults from `resize all`
-— for all topics or the node's, put the library's defaults back on every card
-on the spot, and arm Save. Positions and edge styles are not touched.
-Consumer i18n keys: `reset sizes`, `reset topic sizes`.
+entry keeps what it had.
+
+**Every saved look has a way back, in the context menu** (since `7.23.134`,
+replacing `reset sizes` / `reset topic sizes`). In edition, the node, the port
+and the edge menus each offer three resets — this one, its kind (`reset topic
+nodes`, `reset topic ports`, `reset same type edges`, the scopes of their
+properties popovers) and `reset all …` — and a reset FORGETS the saved value,
+the element's own and the defaults of its scope, so the library's default
+comes back on the spot and Save writes the cleared entries. The node reset is
+offered in every view and forgets size, colours, line width and figure; the
+ports have their own (shape and radius); no reset moves a node. Consumer i18n
+keys: `reset node`, `reset topic nodes`, `reset all nodes`, `reset port`,
+`reset topic ports`, `reset all ports`, `reset edge`, `reset same type edges`,
+`reset all edges`.
+
+**An edge is saved only where it differs from what it INHERITS** (since
+`7.23.134`): its hook's default in the parent topic, else the topic's, else the
+library's. It used to be "any line width but 2", and the library's width for an
+edge between two topics is 1.6, so every Save froze every such edge with its
+width and its theme's colour — a theme toggle no longer re-themed it after a
+reload. `reset all edges` clears what the old Save froze.
+
+**The browser's own menu never opens over the graph** (since `7.23.133`): G6's
+context-menu plugin cancels the event `@antv/g` synthesises from `pointerdown`,
+not the DOM's `contextmenu`, so the container cancels that one (a popover's form
+field keeps it, for paste). An edge has a menu in edition (`edge properties`,
+`unlink`).
+
+**The rest of the 7.23.133–7.23.140 round, in one place:**
+
+- **The legend keeps its order** (`7.23.135`): its chips are alphabetical,
+  always, and the main topic takes no seat of its own (its gold star and bold
+  name tell it apart) — starring a topic no longer moves the strip.
+- **Never a blank viewport** (`7.23.137`). A camera is saved by the node
+  nearest the middle of the viewport (or the anchor), a saved camera whose
+  pixel is off screen is not restored, and after any placement — a restore, a
+  refresh or a global fold holding a node still, a saved arrangement opened
+  with no camera — a viewport with no node in it is fitted. It used to save
+  the first root of the tree wherever it was, and a reload whose layout moved
+  by a hair showed the tree in the minimap and nothing in the view.
+- **The toolbar in three parts** (`7.23.137`): left, how the graph is built
+  (layout, operation mode); center, how it is shown (fold pair, node views);
+  right, what it is asked (find, refresh, raw json).
+- **The topics view opens the graph as it was left** (`7.23.138`–`7.23.140`).
+  `C_YUI_TREEDB_TOPICS` has a `graph` button left of `raw json`, in the
+  landing and with a topic open; its route is `card_action_routes.graph`
+  without its `/{topic}`, and its click navigates to
+  `yui_shell_last_route_under()` of that route, so a focused topic
+  (`<graph>/<topic>`) comes back with it. The cards dropped their graph icon
+  — its topic segment was a focus, laid over whatever the reader had left —
+  and show instead, from the desc with no request, the topic's version, its
+  number of columns, the topics it hangs from (`↑ parents`) and the ones
+  hanging from it (`↓ children`).
 
 **A port has a shape, and its own properties popover** (since `7.23.81`).
 G6 draws every port as a circle — `drawPortShapes` upserts a `Circle` and
@@ -1527,18 +1596,31 @@ them:
 | control | what it does |
 |---|---|
 | the chip body | **show / hide** the topic. A hidden topic leaves the MODEL, not just the drawing: no card, no pill counts it, no edge reaches it, and whatever hung from it alone has no parent any more. The name is struck through and the count is the total. |
-| `★` / `☆` | the **main topic**: the trunk the tree hangs from. Filled on the main one (a mark, not a button — the main topic cannot be hidden, because hiding the trunk turns everything into roots, which is the pile); hollow on the others, where it moves the star. |
+| `★` / `☆` | the **main topic**: the trunk the tree hangs from, always a **hierarchical** topic (hooked to itself); the hollow star appears only on the other hierarchical topics, and only when there are two or more (`7.23.142`). Filled on the main one (a mark, not a button — the main topic cannot be hidden, because hiding the trunk turns everything into roots, which is the pile); hollow on the others, where it moves the star. |
 | `+N` | the topic's **loose records**: the ones that should hang from the main tree and do not (a device with no place). Counted here, shown only on request. |
 | `⌖` | **highlight** the topic — the focus, with `reveal: "all"`. |
 
-The **main topic is deduced** when none is chosen: the topic whose hooks reach
-the most OTHER topics, a self-referent hook breaking a tie (a tree of places
-over a flat list of groups). On the yunovatios central that is `places` (it
-reaches places, devices, users and controllers); `device_types` reaches one.
-An `extended` topic (hooks, no fkeys) never wins: the engine draws no edge
-from one, so its records hang nothing. A treedb where no topic reaches
-another has no trunk, and every topic is a tree of its own — the behaviour
-before this existed.
+**Only a HIERARCHICAL topic can be the main one** (since `7.23.142`): a topic
+hooked to ITSELF — places inside places, groups inside groups, roles inside
+roles (`fold_is_hierarchical()`). A topic that only reaches OTHER topics is a
+list with children, and the old rule (*the topic whose hooks reach the most
+others*) drew the agent's treedb from `yunos` instead of `realms`. In order:
+
+1. the reader's pick (the star), if it is hierarchical — a saved pick the rule
+   refuses is ignored;
+2. the topic the schema **marks**, `main_topic: true` on the topic, sent in the
+   desc by SDK 7.19+ (`tranger2_topic_desc()`); the schema allows one, and only
+   on a topic hooked to itself;
+3. the hierarchical topic that reaches the most other topics, schema order
+   breaking a tie.
+
+In every treedb of the SDK and the apps there is exactly one hierarchical
+topic (`places`, `device_groups`, `systems`, `roles`, `realms`), so the mark
+only has something to decide once a schema grows a second one. A treedb with
+no topic hooked to itself has no trunk, and every topic is a tree of its own.
+
+(Not the engine's card tier: a topic with hooks AND fkeys is an `entity` card
+— it was called `hierarchical` until `7.23.142` — and that only sizes a card.)
 
 What the main topic governs, in `treedb_fold_model.js`:
 
@@ -1560,13 +1642,17 @@ Three edges of it: the URL wins over the strip (a route that lands on a hidden
 topic shows it first, or it would highlight nothing and say nothing about
 why); the find searches hidden topics too and counts them apart (`3 matches
 (+2 in hidden topics)`), because `0` alone reads as *does not exist* when it
-means *is hidden*; and moving the star reopens the tree at `expand_depth`,
-since other roots are another tree.
+means *is hidden*; and moving the star reopens the tree at the reader's fold
+level, counted from the new roots, since other roots are another tree.
 
 Wiring: the engine publishes `EV_LEGEND_STATE` after every reconcile — one
 entry per topic (hidden ones included) with colour, total, visible, loose and
-flags, plus the main topic — and the view paints the strip from that and
-nothing else. The strip's clicks are `EV_LEGEND_TOPIC {topic, action}` with
+flags, plus the main topic and `fold: {topic, level, levels}` for the toolbar's
+stepper — and the view paints the strip and the stepper from that and nothing
+else. A step is `EV_EXPAND_LEVEL` / `EV_COLLAPSE_LEVEL` (internal); the view
+persists `fold_level` and forwards `EV_SET_FOLD_LEVEL {level}` (the engine's
+`EV_EXPAND_ALL` / `EV_COLLAPSE_ALL` are gone). Stepper keys: `expand one
+level`, `collapse one level`, `fold level`, `level`. The strip's clicks are `EV_LEGEND_TOPIC {topic, action}` with
 `action` one of `toggle`, `main`, `loose`, `focus`; the view persists and
 forwards them as `EV_SET_HIDDEN_TOPICS`, `EV_SET_MAIN_TOPIC`,
 `EV_SET_LOOSE_TOPICS`. Consumer i18n keys: `show topic`, `hide topic`,