@yuneta/gobj-ui 7.0.1 → 7.2.0

package/README.md

@@ -491,6 +491,37 @@ The buttons of that toolbar never shrink. When the row runs out of room, the
 url is what gives way, cut with an ellipsis, and the whole value stays in the
 `title` and the `aria-label`.
 
+### Reading a topic table: filters, columns, CSV
+
+`C_YUI_TREEDB_TOPIC_WITH_FORM` had one global search box over the loaded rows.
+Three tools join it, each behind its own flag, all **on** by default:
+
+| attr | what it adds |
+|---|---|
+| `with_header_filters` | a filter box in the header of each column a match means something on |
+| `with_columns_button` | a dialog that ticks which columns the table shows |
+| `with_export_button` | downloads what the table holds as CSV |
+
+**Not every column gets a filter box, on purpose.** A hook holds children, a
+dict holds a subtree, and a date cell shows a formatted string over an epoch
+number — a text match against the raw value there answers a question nobody
+asked, so those columns get no box rather than a box that lies. A `boolean`
+gets a tristate tick, an `enum` gets a list of its own values, and an `fkey`
+gets a box whose match stringifies the value first, because *which rows point
+at X* is the question fkey columns exist to answer and a fkey arrives as a ref
+string, a list of them or a dict.
+
+The search box and the header filters are **separate layers**: clearing the
+search does not silently drop the column filters. The CSV carries what the
+table HOLDS — the loaded rows, the visible columns, both filters applied, which
+is what the reader is looking at. It is not the topic: a server-side dump of
+every node is not something this view can stream, and the button's title says
+so.
+
+Searching is a user action, so it crosses the FSM (`EV_SEARCH`) like the rest;
+it used to call `tabulator.setFilter` straight from the DOM handler, where the
+`machine` trace could not see it.
+
 ### Read-only treedbs: `readonly`
 
 `C_YUI_TREEDB_TOPICS` and `C_YUI_TREEDB_GRAPH` take a **`readonly`** attr; the
@@ -530,6 +561,31 @@ Two implementation notes worth keeping:
   still arrive from a keyboard path or a form that outlived the flag, and an
   ignored write is exactly the behaviour this whole change exists to stop.
 
+### Finding a node in the graph
+
+`C_YUI_TREEDB_GRAPH` carries a find box in the middle of its toolbar. It
+matches the term against the node's **label**, its id and its topic name, puts
+every match in the same amber `active` state the topic focus uses, and centres
+the viewport on them.
+
+Two details that are not decoration:
+
+- it matches the **label**, not only the id. On a topic keyed by `rowid`,
+  `uuid` or `qualified` the id is a counter or a path and the name a human
+  knows the record by lives in a secondary key — the same reason `node_label()`
+  exists.
+- it **says how many** it found. A graph that did not move looks identical
+  whether nothing matched or the only match was already on screen, so the count
+  is shown next to the box (hidden while the box is empty; a typed term that
+  matches nothing shows `0`, which is an answer).
+
+The find and the topic focus **share the highlight**: starting one clears the
+other. Two amber sets at once would say nothing about either.
+
+Wiring: the box sends `EV_FIND_NODES {text}` to the view, which forwards it to
+`C_G6_NODES_TREE`; the graph answers `EV_FIND_RESULT {term, matches}`, which the
+view declares like every other event its child publishes.
+
 ### C_YUI_TREEDB_SCHEMA — the treedb drawn the way its `.c` draws it
 
 A landing view that draws a treedb the way its schema literal draws it in ASCII