@yuneta/gobj-ui 7.23.51 → 7.23.52

package/README.md

@@ -642,16 +642,32 @@ url is what gives way, cut with an ellipsis, and the whole value stays in the
 
 ### Reading a topic a page at a time
 
+> ⚠️ **`with_remote_paging` is OFF in every consumer, and must stay off until
+> linking works with a partial topic.** A record's link picker is built from
+> the rows the PARENT topic's table holds — `build_fkey_options()` asks it
+> with `get_topic_data`, which answers `tabulator.getData()` — and with paging
+> that is one page. So the picker offers 200 of the 5891 possible parents (the
+> right one is usually not among them), and a record whose parent is not on
+> the loaded page opens with an fkey the form cannot match, which saving then
+> drops. A treedb is a **memory database** — the backend holds the topic in
+> RAM either way — so paging buys little and costs the links. The machinery
+> below stays, working and tested, for the day linking learns to ask the
+> BACKEND for a parent instead of the sibling table.
+>
+> **Local pagination is not affected and stays on.** `getData()` answers the
+> WHOLE dataset whatever page is on screen, so paginating the DISPLAY is safe;
+> only paginating the FETCH is not. `page_size` sets the display page for both
+> paths.
+
 `C_YUI_TREEDB_TOPICS` takes **`with_remote_paging`** (off by default) and
 forwards it to every topic table: the table pulls the page it is showing
 instead of the host pushing the whole topic down. It needs the SDK's `nodes`
 with `from` / `limit` (see `YUNO_TREEDB.md` §5.3).
 
-**The page size is generous on purpose** (`page_size`, 200). A treedb that
-fits in one page behaves exactly as it did — paginator hidden, every filter
-seeing every row — so nothing that exists today changes. Only a topic that
-does NOT fit pays for paging, and for that one loading it whole was never an
-option.
+**The page size is generous on purpose** (`page_size`, 200 when paging). A
+treedb that fits in one page behaves exactly as it did — paginator hidden,
+every filter seeing every row. Only a topic that does NOT fit pays for paging,
+and for that one loading it whole was never an option.
 
 **Safe against a backend that cannot page:** it answers the whole list, which
 `nodes_answer()` reads as one page. That is the truth, and it is why the table

package/dist/gobj-ui.cjs.js

@@ -20534,7 +20534,8 @@ var attrs_table$6 = [
 	(0, _yuneta_gobj_js.SDATA)(_yuneta_gobj_js.data_type_t.DTP_POINTER, "gobj_remote_yuno", 0, null, "Remote yuno for data fetching"),
 	(0, _yuneta_gobj_js.SDATA)(_yuneta_gobj_js.data_type_t.DTP_STRING, "treedb_name", 0, null, "Remote TreeDB service name"),
 	(0, _yuneta_gobj_js.SDATA)(_yuneta_gobj_js.data_type_t.DTP_JSON, "descs", 0, null, "Description of topics"),
-	(0, _yuneta_gobj_js.SDATA)(_yuneta_gobj_js.data_type_t.DTP_BOOLEAN, "with_remote_paging", 0, false, "Each topic table pulls its rows a PAGE at a time (`nodes` from/limit) instead of loading the topic whole. Safe against a backend that cannot page: it answers the whole list, which the table reads as one page"),
+	(0, _yuneta_gobj_js.SDATA)(_yuneta_gobj_js.data_type_t.DTP_BOOLEAN, "with_remote_paging", 0, false, "Each topic table pulls its rows a PAGE at a time (`nodes` from/limit) instead of loading the topic whole. ⚠️ DO NOT TURN THIS ON: a partial topic BREAKS LINKING -- the link picker of a record is built from the rows the PARENT topic's table holds, which with paging is one page, so the right parent is usually not offered and an existing link the form cannot match is dropped on save. Off in every consumer until linking asks the backend instead of the sibling table"),
+	(0, _yuneta_gobj_js.SDATA)(_yuneta_gobj_js.data_type_t.DTP_INTEGER, "page_size", 0, 0, "Rows per page of each topic table (the DISPLAY; the fetch is whole). 0 leaves the table's own default"),
 	(0, _yuneta_gobj_js.SDATA)(_yuneta_gobj_js.data_type_t.DTP_BOOLEAN, "with_selection_bar", 0, false, "Each topic table shows the shared selection bar (\"N selected\" + a way out) above it while in edition mode. OFF by default: the bar takes its words from the HOST's i18n, so a host that turns it on must define \"{{n}} selected\" and \"clear selection\""),
 	(0, _yuneta_gobj_js.SDATA)(_yuneta_gobj_js.data_type_t.DTP_BOOLEAN, "system", 0, false, "Manage system topics (true) or user topics (false)"),
 	(0, _yuneta_gobj_js.SDATA)(_yuneta_gobj_js.data_type_t.DTP_STRING, "tabs_style", 0, "is-toggle is-fullwidth", "Bulma tab styling"),
@@ -21351,6 +21352,7 @@ function process_treedb_descs$1(gobj) {
 			topic_name: key,
 			desc,
 			with_remote_paging: (0, _yuneta_gobj_js.gobj_read_bool_attr)(gobj, "with_remote_paging"),
+			page_size: (0, _yuneta_gobj_js.gobj_read_integer_attr)(gobj, "page_size"),
 			with_selection_bar: (0, _yuneta_gobj_js.gobj_read_bool_attr)(gobj, "with_selection_bar")
 		};
 		let id = `${(0, _yuneta_gobj_js.gobj_name)(gobj)}?${desc.topic_name}`;
@@ -22912,8 +22914,8 @@ var attrs_table$5 = [
 	(0, _yuneta_gobj_js.SDATA)(_yuneta_gobj_js.data_type_t.DTP_BOOLEAN, "with_export_button", 0, true, "Button toolbar EXPORT (download as CSV what the table holds)"),
 	(0, _yuneta_gobj_js.SDATA)(_yuneta_gobj_js.data_type_t.DTP_BOOLEAN, "with_header_filters", 0, true, "Per-column filter box in the table header, on the columns a text/number match means something (not hooks, fkeys or json)"),
 	(0, _yuneta_gobj_js.SDATA)(_yuneta_gobj_js.data_type_t.DTP_BOOLEAN, "with_inline_edit", 0, true, "Edit a writable scalar cell in place while in edition mode (the record form keeps the rest)"),
-	(0, _yuneta_gobj_js.SDATA)(_yuneta_gobj_js.data_type_t.DTP_BOOLEAN, "with_remote_paging", 0, false, "Pull the topic a PAGE at a time from the backend (`nodes` from/limit) instead of loading it whole. Needs a backend that pages"),
-	(0, _yuneta_gobj_js.SDATA)(_yuneta_gobj_js.data_type_t.DTP_INTEGER, "page_size", 0, 200, "Rows per page when with_remote_paging. Generous on purpose: a treedb that fits in one page behaves exactly as it did, paginator hidden and every filter seeing every row"),
+	(0, _yuneta_gobj_js.SDATA)(_yuneta_gobj_js.data_type_t.DTP_BOOLEAN, "with_remote_paging", 0, false, "Pull the topic a PAGE at a time from the backend (`nodes` from/limit) instead of loading it whole. Needs a backend that pages. ⚠️ DO NOT TURN THIS ON: it breaks LINKS -- see the note above the tabulator settings. It is off in every consumer until linking works with a partial topic"),
+	(0, _yuneta_gobj_js.SDATA)(_yuneta_gobj_js.data_type_t.DTP_INTEGER, "page_size", 0, 0, "Rows per page. 0 leaves the `tabulator_settings` value alone. With with_remote_paging it is also the size of each fetch (200 when unset)"),
 	(0, _yuneta_gobj_js.SDATA)(_yuneta_gobj_js.data_type_t.DTP_BOOLEAN, "with_in_row_edit_icons", 0, true, "Add a last column with internal EDIT/DELETE icon"),
 	(0, _yuneta_gobj_js.SDATA)(_yuneta_gobj_js.data_type_t.DTP_BOOLEAN, "editable", 0, false, "Edit state"),
 	(0, _yuneta_gobj_js.SDATA)(_yuneta_gobj_js.data_type_t.DTP_BOOLEAN, "with_checkbox", 0, true, "Auxiliary first column to select rows"),
@@ -23834,6 +23836,19 @@ function create_tabulator(gobj) {
 			}
 		});
 	}
+	if (!(0, _yuneta_gobj_js.gobj_read_bool_attr)(gobj, "with_remote_paging")) {
+		let page_size = (0, _yuneta_gobj_js.gobj_read_integer_attr)(gobj, "page_size");
+		if (page_size > 0 && tabulator_settings.pagination) {
+			tabulator_settings.paginationSize = page_size;
+			tabulator_settings.paginationSizeSelector = [
+				50,
+				100,
+				200,
+				500,
+				true
+			];
+		}
+	}
 	let remembered_size = load_page_size(gobj);
 	if (remembered_size !== null && tabulator_settings.pagination) tabulator_settings.paginationSize = remembered_size;
 	gobj.priv._page_size = tabulator_settings.paginationSize;

package/dist/gobj-ui.es.js

@@ -20529,7 +20529,8 @@ var attrs_table$6 = [
 	SDATA(data_type_t.DTP_POINTER, "gobj_remote_yuno", 0, null, "Remote yuno for data fetching"),
 	SDATA(data_type_t.DTP_STRING, "treedb_name", 0, null, "Remote TreeDB service name"),
 	SDATA(data_type_t.DTP_JSON, "descs", 0, null, "Description of topics"),
-	SDATA(data_type_t.DTP_BOOLEAN, "with_remote_paging", 0, false, "Each topic table pulls its rows a PAGE at a time (`nodes` from/limit) instead of loading the topic whole. Safe against a backend that cannot page: it answers the whole list, which the table reads as one page"),
+	SDATA(data_type_t.DTP_BOOLEAN, "with_remote_paging", 0, false, "Each topic table pulls its rows a PAGE at a time (`nodes` from/limit) instead of loading the topic whole. ⚠️ DO NOT TURN THIS ON: a partial topic BREAKS LINKING -- the link picker of a record is built from the rows the PARENT topic's table holds, which with paging is one page, so the right parent is usually not offered and an existing link the form cannot match is dropped on save. Off in every consumer until linking asks the backend instead of the sibling table"),
+	SDATA(data_type_t.DTP_INTEGER, "page_size", 0, 0, "Rows per page of each topic table (the DISPLAY; the fetch is whole). 0 leaves the table's own default"),
 	SDATA(data_type_t.DTP_BOOLEAN, "with_selection_bar", 0, false, "Each topic table shows the shared selection bar (\"N selected\" + a way out) above it while in edition mode. OFF by default: the bar takes its words from the HOST's i18n, so a host that turns it on must define \"{{n}} selected\" and \"clear selection\""),
 	SDATA(data_type_t.DTP_BOOLEAN, "system", 0, false, "Manage system topics (true) or user topics (false)"),
 	SDATA(data_type_t.DTP_STRING, "tabs_style", 0, "is-toggle is-fullwidth", "Bulma tab styling"),
@@ -21346,6 +21347,7 @@ function process_treedb_descs$1(gobj) {
 			topic_name: key,
 			desc,
 			with_remote_paging: gobj_read_bool_attr(gobj, "with_remote_paging"),
+			page_size: gobj_read_integer_attr(gobj, "page_size"),
 			with_selection_bar: gobj_read_bool_attr(gobj, "with_selection_bar")
 		};
 		let id = `${gobj_name(gobj)}?${desc.topic_name}`;
@@ -22907,8 +22909,8 @@ var attrs_table$5 = [
 	SDATA(data_type_t.DTP_BOOLEAN, "with_export_button", 0, true, "Button toolbar EXPORT (download as CSV what the table holds)"),
 	SDATA(data_type_t.DTP_BOOLEAN, "with_header_filters", 0, true, "Per-column filter box in the table header, on the columns a text/number match means something (not hooks, fkeys or json)"),
 	SDATA(data_type_t.DTP_BOOLEAN, "with_inline_edit", 0, true, "Edit a writable scalar cell in place while in edition mode (the record form keeps the rest)"),
-	SDATA(data_type_t.DTP_BOOLEAN, "with_remote_paging", 0, false, "Pull the topic a PAGE at a time from the backend (`nodes` from/limit) instead of loading it whole. Needs a backend that pages"),
-	SDATA(data_type_t.DTP_INTEGER, "page_size", 0, 200, "Rows per page when with_remote_paging. Generous on purpose: a treedb that fits in one page behaves exactly as it did, paginator hidden and every filter seeing every row"),
+	SDATA(data_type_t.DTP_BOOLEAN, "with_remote_paging", 0, false, "Pull the topic a PAGE at a time from the backend (`nodes` from/limit) instead of loading it whole. Needs a backend that pages. ⚠️ DO NOT TURN THIS ON: it breaks LINKS -- see the note above the tabulator settings. It is off in every consumer until linking works with a partial topic"),
+	SDATA(data_type_t.DTP_INTEGER, "page_size", 0, 0, "Rows per page. 0 leaves the `tabulator_settings` value alone. With with_remote_paging it is also the size of each fetch (200 when unset)"),
 	SDATA(data_type_t.DTP_BOOLEAN, "with_in_row_edit_icons", 0, true, "Add a last column with internal EDIT/DELETE icon"),
 	SDATA(data_type_t.DTP_BOOLEAN, "editable", 0, false, "Edit state"),
 	SDATA(data_type_t.DTP_BOOLEAN, "with_checkbox", 0, true, "Auxiliary first column to select rows"),
@@ -23829,6 +23831,19 @@ function create_tabulator(gobj) {
 			}
 		});
 	}
+	if (!gobj_read_bool_attr(gobj, "with_remote_paging")) {
+		let page_size = gobj_read_integer_attr(gobj, "page_size");
+		if (page_size > 0 && tabulator_settings.pagination) {
+			tabulator_settings.paginationSize = page_size;
+			tabulator_settings.paginationSizeSelector = [
+				50,
+				100,
+				200,
+				500,
+				true
+			];
+		}
+	}
 	let remembered_size = load_page_size(gobj);
 	if (remembered_size !== null && tabulator_settings.pagination) tabulator_settings.paginationSize = remembered_size;
 	gobj.priv._page_size = tabulator_settings.paginationSize;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yuneta/gobj-ui",
-  "version": "7.23.51",
+  "version": "7.23.52",
   "type": "module",
   "main": "dist/gobj-ui.cjs.js",
   "module": "dist/gobj-ui.es.js",

package/src/c_yui_treedb_topic_with_form.js

@@ -188,8 +188,8 @@ SDATA(data_type_t.DTP_BOOLEAN,  "with_columns_button",       0,  true,   "Button
 SDATA(data_type_t.DTP_BOOLEAN,  "with_export_button",        0,  true,   "Button toolbar EXPORT (download as CSV what the table holds)"),
 SDATA(data_type_t.DTP_BOOLEAN,  "with_header_filters",       0,  true,   "Per-column filter box in the table header, on the columns a text/number match means something (not hooks, fkeys or json)"),
 SDATA(data_type_t.DTP_BOOLEAN,  "with_inline_edit",          0,  true,   "Edit a writable scalar cell in place while in edition mode (the record form keeps the rest)"),
-SDATA(data_type_t.DTP_BOOLEAN,  "with_remote_paging",        0,  false,  "Pull the topic a PAGE at a time from the backend (`nodes` from/limit) instead of loading it whole. Needs a backend that pages"),
-SDATA(data_type_t.DTP_INTEGER,  "page_size",                 0,  200,    "Rows per page when with_remote_paging. Generous on purpose: a treedb that fits in one page behaves exactly as it did, paginator hidden and every filter seeing every row"),
+SDATA(data_type_t.DTP_BOOLEAN,  "with_remote_paging",        0,  false,  "Pull the topic a PAGE at a time from the backend (`nodes` from/limit) instead of loading it whole. Needs a backend that pages. ⚠️ DO NOT TURN THIS ON: it breaks LINKS -- see the note above the tabulator settings. It is off in every consumer until linking works with a partial topic"),
+SDATA(data_type_t.DTP_INTEGER,  "page_size",                 0,  0,      "Rows per page. 0 leaves the `tabulator_settings` value alone. With with_remote_paging it is also the size of each fetch (200 when unset)"),
 SDATA(data_type_t.DTP_BOOLEAN,  "with_in_row_edit_icons",    0,  true,   "Add a last column with internal EDIT/DELETE icon"),
 
 SDATA(data_type_t.DTP_BOOLEAN,  "editable",             0,  false,  "Edit state"),
@@ -1393,16 +1393,29 @@ function create_tabulator(gobj)
     let tabulator_settings = json_deep_copy(gobj_read_attr(gobj, "tabulator_settings"));
 
     /*  Remote paging: the TABLE pulls, instead of the host pushing the whole
-     *  topic down. The page size is generous on purpose — a treedb that fits
-     *  in one page behaves exactly as it did before, with the paginator
-     *  hidden and every filter seeing every row. Only a topic that does NOT
-     *  fit pays for paging, and for that one loading it whole was never an
-     *  option anyway.
+     *  topic down. Only a topic that does NOT fit pays for it, and for that
+     *  one loading it whole was never an option anyway.
      *
      *  `filterMode: "local"` says the plain truth: the header filters and the
      *  search box work on the page that is loaded. Same as the tranger
      *  browser's Rows card, and for the same reason — the alternative is
      *  pushing every filter to the backend and changing what "search" means.
+     *
+     *  ⚠️ AND IT IS OFF IN EVERY CONSUMER, because it BREAKS LINKING.
+     *  `build_fkey_options()` asks the PARENT topic's table for the rows it
+     *  holds (`get_topic_data` -> `tabulator.getData()`), and with paging
+     *  that is one page. So the link picker offers 200 of the 5891 possible
+     *  parents -- the right one is usually not among them -- and a record
+     *  whose parent is not on the loaded page opens with an fkey the form
+     *  cannot match, which saving then drops. Local pagination has none of
+     *  this: `getData()` answers the WHOLE dataset whatever page is on
+     *  screen, so paginating the DISPLAY is safe and only paginating the
+     *  FETCH is not.
+     *
+     *  A treedb is a memory database -- the backend holds the topic in RAM
+     *  either way -- so paging buys little and costs the links. It stays
+     *  here, working and tested, for the day linking learns to ask the
+     *  BACKEND for a parent instead of the sibling table.
      */
     if(gobj_read_bool_attr(gobj, "with_remote_paging")) {
         let page_size = gobj_read_integer_attr(gobj, "page_size") || 200;
@@ -1428,6 +1441,20 @@ function create_tabulator(gobj)
         });
     }
 
+    /*  Rows per page for the LOCAL paginator too, when the host asks for
+     *  one: with the fetch no longer paged, `page_size` is the only thing
+     *  left that says how many rows a reader wants in front of them, and a
+     *  host that had 200 should not drop to 25 for having stopped paging the
+     *  fetch. The sizes offered go up with it -- a selector that cannot name
+     *  the size in use is a selector Tabulator has to patch itself.  */
+    if(!gobj_read_bool_attr(gobj, "with_remote_paging")) {
+        let page_size = gobj_read_integer_attr(gobj, "page_size");
+        if(page_size > 0 && tabulator_settings.pagination) {
+            tabulator_settings.paginationSize = page_size;
+            tabulator_settings.paginationSizeSelector = [50, 100, 200, 500, true];
+        }
+    }
+
     /*  The size the reader picked last time, which outranks both defaults
      *  above. Applied here, once the two paths have set theirs, so it is
      *  written in ONE place -- and applied to `paginationSize` only: the

package/src/c_yui_treedb_topics.js

@@ -32,6 +32,7 @@ import {
     gobj_short_name,
     gobj_read_str_attr,
     gobj_read_bool_attr,
+    gobj_read_integer_attr,
     gobj_start,
     gobj_stop,
     gobj_is_running,
@@ -75,7 +76,8 @@ SDATA(data_type_t.DTP_POINTER,  "subscriber",       0,  null,   "Subscriber of o
 SDATA(data_type_t.DTP_POINTER,  "gobj_remote_yuno", 0,  null,   "Remote yuno for data fetching"),
 SDATA(data_type_t.DTP_STRING,   "treedb_name",      0,  null,   "Remote TreeDB service name"),
 SDATA(data_type_t.DTP_JSON,     "descs",            0,  null,   "Description of topics"),
-SDATA(data_type_t.DTP_BOOLEAN,  "with_remote_paging",   0,  false,  "Each topic table pulls its rows a PAGE at a time (`nodes` from/limit) instead of loading the topic whole. Safe against a backend that cannot page: it answers the whole list, which the table reads as one page"),
+SDATA(data_type_t.DTP_BOOLEAN,  "with_remote_paging",   0,  false,  "Each topic table pulls its rows a PAGE at a time (`nodes` from/limit) instead of loading the topic whole. ⚠️ DO NOT TURN THIS ON: a partial topic BREAKS LINKING -- the link picker of a record is built from the rows the PARENT topic's table holds, which with paging is one page, so the right parent is usually not offered and an existing link the form cannot match is dropped on save. Off in every consumer until linking asks the backend instead of the sibling table"),
+SDATA(data_type_t.DTP_INTEGER,  "page_size",            0,  0,      "Rows per page of each topic table (the DISPLAY; the fetch is whole). 0 leaves the table's own default"),
 SDATA(data_type_t.DTP_BOOLEAN,  "with_selection_bar",   0,  false,  "Each topic table shows the shared selection bar (\"N selected\" + a way out) above it while in edition mode. OFF by default: the bar takes its words from the HOST's i18n, so a host that turns it on must define \"{{n}} selected\" and \"clear selection\""),
 SDATA(data_type_t.DTP_BOOLEAN,  "system",           0,  false,  "Manage system topics (true) or user topics (false)"),
 SDATA(data_type_t.DTP_STRING,   "tabs_style",       0,  "is-toggle is-fullwidth", "Bulma tab styling"),
@@ -1041,6 +1043,7 @@ function process_treedb_descs(gobj)
             topic_name: key,
             desc: desc,
             with_remote_paging: gobj_read_bool_attr(gobj, "with_remote_paging"),
+            page_size: gobj_read_integer_attr(gobj, "page_size"),
             with_selection_bar: gobj_read_bool_attr(gobj, "with_selection_bar")
         };