@yuneta/gobj-ui 7.23.158 → 7.23.160

package/README.md

@@ -925,6 +925,30 @@ so it survived that — two light islands over a dark canvas.
 (all tooltips, so a host that has not defined them shows the key on hover and
 nothing else breaks).
 
+### The wheel over HTML nodes: `yui_graph_forward_wheel`
+
+G6's HTML nodes are drawn in a DOM layer **beside** the canvas element, and
+they pass on six pointer events and not the wheel. `scroll-canvas` listens on
+the canvas element and `zoom-canvas` reads G's wheel, which comes from that
+same element. So a wheel over an HTML card reaches neither: the graph does not
+scroll and does not zoom.
+
+`yui_graph_forward_wheel(graph, $host)` catches the wheel on the element G6 was
+mounted in and dispatches it again on the canvas element, with its deltas, its
+position and its modifiers. Both behaviors then take it as a wheel over empty
+canvas. It returns the function that removes the listener; call it before the
+graph is destroyed.
+
+```js
+priv.unforward_wheel = yui_graph_forward_wheel(graph, priv.$canvas);
+// ... in the teardown, before graph.destroy():
+priv.unforward_wheel();
+```
+
+An element that must scroll by itself inside the graph (a popover) stops the
+wheel with `stopPropagation()` before it reaches `$host`.
+`C_YUI_TREEDB_SCHEMA` uses it; `C_G6_NODES_TREE` does not yet.
+
 ### The anchor: one element the camera holds
 
 The same crosshairs button is in all three graphs' toolbars, drawn once in
@@ -1797,6 +1821,17 @@ schema question; that one answers the data question.
 The demo `test-app/schema.html` mounts it alone against the real yuneta agent
 schema, so the drawing can be held against the ASCII one in its `.c`.
 
+**Its camera is the family's** (since `7.23.160`). It has a toolbar with the
+`yui_graph_camera.js` cluster (zoom in, zoom out, the readout, fit, `1:1`), and
+it takes the wheel the same way as the other graphs: the wheel **scrolls**,
+Ctrl + wheel zooms, and a pinch zooms on a touch screen. This is true over the
+cards too, through `yui_graph_forward_wheel()`: the cards cover most of this
+drawing, and without it the wheel worked only in the gaps. It still never fits
+itself when it appears; fit is a button. The toolbar buttons fire
+`EV_ZOOM_IN`, `EV_ZOOM_OUT`, `EV_ZOOM_RESET` and `EV_CENTER` to the view
+itself, so a host declares nothing. `wide` (default `40px`) sets the button
+height.
+
 **Contract:**
 
 - Attributes: `subscriber`, `descs` (`{topic_name: desc}`, the schema),
@@ -1952,7 +1987,12 @@ backend** — asking is an action and belongs in the view's own FSM:
 |---|---|
 | `yui_asset_id(ref)` / `yui_asset_ids(ref)` | the id(s) a column names. A link comes back in whichever shape the READER asked for — the stored `"assets^<id>^as_foto"`, the bare `"<id>"` that `fkey_only_id` collapses it to, or an expanded `{id}` — and either alone or in a list, because an unset single-valued fkey is still an empty list. All of them are read; an empty column answers nothing rather than throwing |
 | `yui_asset_src(answer)` | the two shapes into one `src`. `null` when the answer carries neither — never an empty string, because `<img src="">` reloads the page in some browsers |
-| `yui_asset_element(answer, opts)` | the element, picked from the **content type the backend stored**: `<img>`, `<video>` or `<audio>`. Video and audio are assets too, and an `<img>` whose src is a film shows the broken box this exists to remove |
+| `yui_asset_kind(content_type)` | `"image"`, `"video"`, `"audio"`, `"pdf"` or `"other"`, from the content type the backend stored (a `; charset=…` parameter is ignored) |
+| `yui_asset_element(answer, opts)` | the element, picked by that kind: `<img>`, `<video>`, `<audio>`, a PDF in an `<iframe>` (the browser's own viewer), or, for any other kind, a card with the content type and an open link. Video and audio are assets too, and an `<img>` whose src is a film shows the broken box this exists to remove |
+| `yui_asset_open_link(answer)` | an `<a target=_blank>` that opens the asset at full size, named through `open in a new tab`. `null` when there is nothing to open |
+| `yui_asset_href(answer)` | `{href, blob}`: the url as it comes, or a `blob:` url over inline bytes. Firefox will not NAVIGATE to a `data:` url (a new tab stays blank) and its PDF viewer does not run on one in a frame, so frames and links need a blob |
+| `yui_asset_file_answer(file)` | the answer a picked `File` would have had: a `url` answer over a `blob:` url of the File itself, so a file not saved yet goes through the same element as a stored one |
+| `yui_asset_release($root)` | revoke every `blob:` url this module made under `$root`, `$root` included. A blob url keeps its bytes alive until revoked and removing the DOM revokes nothing, so call it on whatever element you drop |
 | `yui_asset_missing(detail, opts)` | the marker, for when there is nothing to show |
 
 **A missing asset is now said out loud.** It used to leave a broken box and
@@ -1979,6 +2019,43 @@ if(id) {
 $box.appendChild(yui_asset_element(answer, {detail: device.foto_name}));
 ```
 
+#### In the treedb views
+
+The treedb form and table show the asset a `file` column names, and they ask
+for it in the same way as a page of rows: the table publishes the request UP
+and its host owns the transport.
+
+```
+C_YUI_TREEDB_TOPIC_WITH_FORM                 C_YUI_TREEDB_TOPICS
+  EV_REQUEST_ASSET {topic_name, req_id, asset_id}  ──►  get-asset asset_id=<id>
+                                                          (service = assets_service)
+  EV_ASSET_LOADED {req_id, answer}  ◄──  the answer, by req_id
+  EV_ASSET_FAILED {req_id, error}   ◄──  a refusal, no backend, or 30 s of silence
+```
+
+- **Form:** when the edit dialog opens, one request goes out per `file` column
+  that names an asset. The answer reaches the form as
+  `EV_SET_FILE_PREVIEW {name, id, answer, error}` and is drawn under the
+  control only while the column still names that id. A picked file needs no
+  request: it is previewed from the `File`.
+- **Table:** a click on a file cell opens a popup with one slot per asset the
+  cell names. Each slot starts as `loading` and is filled by its own answer.
+
+Set the service on the host. `"assets"` is the default, and it is what a yuno
+names its `C_ASSETS`; an empty string turns the requests off:
+
+```js
+gobj_create_service("#topics-mydb", "C_YUI_TREEDB_TOPICS", {
+    gobj_remote_yuno: remote,
+    treedb_name:      "treedb_mydb",
+    assets_service:   "assets"
+}, gobj);
+```
+
+The user needs the `read` permission of that service. The service is not the
+one the connection was opened for, so a user who is not root must also hold a
+role in it, or the ievent gate refuses to route the command there.
+
 ### JSON viewer — `setup_json_pad`
 
 `setup_json_pad(self)` opens a **blank JSON pad** (`C_YUI_JSON_PAD`) in a