mkui 0.3.0__tar.gz → 0.3.2__tar.gz

{mkui-0.3.0 → mkui-0.3.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mkui
-Version: 0.3.0
+Version: 0.3.2
 Summary: Config-driven, zero-dependency web GUI framework with dockable panes
 Author: Mark Kim
 License-Expression: Apache-2.0
@@ -211,7 +211,7 @@ mkio server and verifies its identity. Connection is two-phase:
     "name": "order-book",
     "version": "1.0",
     "protocol": "1.0",
-    "mkio": "0.2",
+    "mkio": "0.3",
     "expr": "1"
   },
   "connected":    { "status.message": "Connected", "status.background": null },
@@ -227,6 +227,15 @@ to the server's `_mkio` service). When `expect` is absent, the `_mkio`
 query still runs to confirm it is an mkio server and to populate
 `mkio.server.*` state paths (name, version, protocol, mkio).
 
+Semver matching is stricter below 1.0, where the minor number carries the
+breaking changes: `"0.3"` accepts 0.3.x and rejects 0.4.0, so pinning
+`mkio` at a pre-1.0 version means every minor release of the library
+invalidates the pin. A stale pin is quiet — the app connects, the
+`incompatible` map is applied, and the statusbar reads "Wrong server"
+while nothing is wrong with the server. Leave `mkio` out unless the app
+truly depends on the library's version, and pin `name` and `version`,
+which are your own, instead.
+
 The same reply says what the server can do, which lands in
 `mkio.server.services` (service name → protocol),
 `mkio.server.versioned` (the tables whose every change it records — see
@@ -802,7 +811,8 @@ python3 -m http.server 8000
 # http://localhost:8000/examples/library-js/
 ```
 
-The mkio-table example requires [mkio](https://pypi.org/project/mkio/):
+The mkio-table example requires [mkio](https://pypi.org/project/mkio/) 0.3.0 or
+later (its `orders` table is versioned):
 
 ```
 cd mkui/static/examples/mkio-table
@@ -824,6 +834,8 @@ Its `orders` table is `versioned = true`, so mkio records every version of every
 
 **All Orders** broadcasts the selected orders' `id` and `symbol`; the **Child Orders** frame listens for the id on its `parent_id` column and **Pending** for the symbol, so a selection filters both (the chips on each toolbar show and pause the links, and a saved layout keeps them). `python control.py` serves the example in place of `mkio serve` and rewires those links from Python a few seconds after a browser connects. The seeder places child orders under pending parents (and some under other children), so the **Order Tree** tab shows the same orders nested by `parent_id`: expand a parent with its caret, place a child order under the selected row with *+ Child Order*, and try the View menu's expand/collapse actions and alt/option-clicking a filter button for the scope row. The toolbar buttons show both styling forms: the **Pending** tab's Fill and Cancel wear a plain `style` map (green, and black on red in capitals) at all times, while the All Orders Cancel turns red only once a pending order is selected, through a rule conditioned on `enabled`.
 
+The `orders` table is `versioned = true`, so mkio records every version of every row in `orders__history`, and `server.toml` writes the four services that expose it — one record's chain, where a record sits in it, the live tape, and the table as at a moment. **All Orders** names them in a `history` block and shows `_mkio_version` beside the data, which puts *Undo*, *Redo* and *As of…* on its toolbar: filling or cancelling an order moves it to a second version, Undo steps it back with a confirmation that says what will change, and *As of…* shows the book as it stood before the seeder's last few minutes, read-only until *Live* re-subscribes. Undo, Redo and *As of…* arrive with the block; the version timeline does not, so All Orders adds a **History** button of its own beside them — a `table.history` action over one selected record — and Record → History… is the same step from the menubar. Either opens that order's version timeline with its diff and blame views. Record → Audit Tape opens a parked query pane over the history table — every recorded version, newest first, live as they land — whose *Go to order* selects the record in All Orders rather than filtering it (a key All Orders' `status` and `notional` filters hide is reported back rather than revealed). An existing `orders.db` picks all this up on the next start: `auto_migrate = "safe"` creates the history table and records every live row as its baseline version.
+
 ## Project layout
 
 ```
@@ -861,9 +873,10 @@ mkui/                    Python package (pip install mkui)
       standalone-json/   Loaded from a static config
       library-js/        Built imperatively from JS
       mkio-table/        Live table backed by mkio query/subpub services
-                         (config-only derived columns, styling rules, and
-                         enable conditions; static/app.js registers an
-                         expression function and the order-detail pane)
+                         (config-only derived columns, styling rules,
+                         enable conditions, and record history over a
+                         versioned orders table; static/app.js registers
+                         an expression function and the order-detail pane)
       history/           Versioned table: the audit tape, the version
                          timeline with diff and blame, record undo/redo,
                          and the table as at a moment (config only)
@@ -872,13 +885,29 @@ tests/
   layout.test.js         Layout tree unit tests (node:test)
   state.test.js          State + connection lifecycle tests (node:test)
   table.test.js          mkio-table pane tests (node:test)
+  pane-filters.test.js   Configured filters, sort, visible: specs and API (node:test)
+  links.test.js          LinkHub and table-to-table linking (node:test)
+  history.test.js        Versioned tables: capabilities, spec, chain logic (node:test)
+  history-pane.test.js   mkio-history pane: versions, diff, blame (node:test)
+  copy.test.js           Clipboard grids: TSV quoting and HTML (node:test)
+  timeparse.test.js      Time detection, parsing, bounds, presets (node:test)
+  icons.test.js          Icon library: every name resolves to an SVG (node:test)
   dialog.test.js         Dialog expression + submission tests (node:test)
   auth.test.js           Authentication module + state lifecycle tests (node:test)
   expressions.test.js    Expression conformance fixtures + mkui wrapper tests (node:test)
   vendor-sync.test.js    lib/expr.js and expr_cases.json match the installed mkio (node:test)
   rich.test.js           Rich text type, mkui function library, clipboard HTML (node:test)
   styles.test.js         mkui.css layout invariants (node:test)
+  tabbar.test.js         Tab bar: drag, reorder, overflow, rename (node:test)
+  tab-focus.test.js      Active tab group and focus routing (node:test)
+  edit-routing.test.js   edit.* actions and shortcuts reach the pane (node:test)
+  pointer-guards.test.js Button/modifier guards on every drag start (node:test)
+  windows-menu.test.js   Windows and layouts menu expansion (node:test)
   layouts.test.js        Saved layouts: format, stores, workspace restore, menu (node:test)
   version.test.js        The four version strings agree (node:test)
   test_cli.py            CLI init/serve tests (unittest)
+  test_control.py        ControlService: push actions to browsers (unittest)
+  test_examples.py       Each example config against its server: the
+                         [mkio.expect] pins, pane services, history
+                         blocks, menu and frame pane ids (unittest)
 ```

{mkui-0.3.0 → mkui-0.3.2}/README.md

@@ -191,7 +191,7 @@ mkio server and verifies its identity. Connection is two-phase:
     "name": "order-book",
     "version": "1.0",
     "protocol": "1.0",
-    "mkio": "0.2",
+    "mkio": "0.3",
     "expr": "1"
   },
   "connected":    { "status.message": "Connected", "status.background": null },
@@ -207,6 +207,15 @@ to the server's `_mkio` service). When `expect` is absent, the `_mkio`
 query still runs to confirm it is an mkio server and to populate
 `mkio.server.*` state paths (name, version, protocol, mkio).
 
+Semver matching is stricter below 1.0, where the minor number carries the
+breaking changes: `"0.3"` accepts 0.3.x and rejects 0.4.0, so pinning
+`mkio` at a pre-1.0 version means every minor release of the library
+invalidates the pin. A stale pin is quiet — the app connects, the
+`incompatible` map is applied, and the statusbar reads "Wrong server"
+while nothing is wrong with the server. Leave `mkio` out unless the app
+truly depends on the library's version, and pin `name` and `version`,
+which are your own, instead.
+
 The same reply says what the server can do, which lands in
 `mkio.server.services` (service name → protocol),
 `mkio.server.versioned` (the tables whose every change it records — see
@@ -782,7 +791,8 @@ python3 -m http.server 8000
 # http://localhost:8000/examples/library-js/
 ```
 
-The mkio-table example requires [mkio](https://pypi.org/project/mkio/):
+The mkio-table example requires [mkio](https://pypi.org/project/mkio/) 0.3.0 or
+later (its `orders` table is versioned):
 
 ```
 cd mkui/static/examples/mkio-table
@@ -804,6 +814,8 @@ Its `orders` table is `versioned = true`, so mkio records every version of every
 
 **All Orders** broadcasts the selected orders' `id` and `symbol`; the **Child Orders** frame listens for the id on its `parent_id` column and **Pending** for the symbol, so a selection filters both (the chips on each toolbar show and pause the links, and a saved layout keeps them). `python control.py` serves the example in place of `mkio serve` and rewires those links from Python a few seconds after a browser connects. The seeder places child orders under pending parents (and some under other children), so the **Order Tree** tab shows the same orders nested by `parent_id`: expand a parent with its caret, place a child order under the selected row with *+ Child Order*, and try the View menu's expand/collapse actions and alt/option-clicking a filter button for the scope row. The toolbar buttons show both styling forms: the **Pending** tab's Fill and Cancel wear a plain `style` map (green, and black on red in capitals) at all times, while the All Orders Cancel turns red only once a pending order is selected, through a rule conditioned on `enabled`.
 
+The `orders` table is `versioned = true`, so mkio records every version of every row in `orders__history`, and `server.toml` writes the four services that expose it — one record's chain, where a record sits in it, the live tape, and the table as at a moment. **All Orders** names them in a `history` block and shows `_mkio_version` beside the data, which puts *Undo*, *Redo* and *As of…* on its toolbar: filling or cancelling an order moves it to a second version, Undo steps it back with a confirmation that says what will change, and *As of…* shows the book as it stood before the seeder's last few minutes, read-only until *Live* re-subscribes. Undo, Redo and *As of…* arrive with the block; the version timeline does not, so All Orders adds a **History** button of its own beside them — a `table.history` action over one selected record — and Record → History… is the same step from the menubar. Either opens that order's version timeline with its diff and blame views. Record → Audit Tape opens a parked query pane over the history table — every recorded version, newest first, live as they land — whose *Go to order* selects the record in All Orders rather than filtering it (a key All Orders' `status` and `notional` filters hide is reported back rather than revealed). An existing `orders.db` picks all this up on the next start: `auto_migrate = "safe"` creates the history table and records every live row as its baseline version.
+
 ## Project layout
 
 ```
@@ -841,9 +853,10 @@ mkui/                    Python package (pip install mkui)
       standalone-json/   Loaded from a static config
       library-js/        Built imperatively from JS
       mkio-table/        Live table backed by mkio query/subpub services
-                         (config-only derived columns, styling rules, and
-                         enable conditions; static/app.js registers an
-                         expression function and the order-detail pane)
+                         (config-only derived columns, styling rules,
+                         enable conditions, and record history over a
+                         versioned orders table; static/app.js registers
+                         an expression function and the order-detail pane)
       history/           Versioned table: the audit tape, the version
                          timeline with diff and blame, record undo/redo,
                          and the table as at a moment (config only)
@@ -852,13 +865,29 @@ tests/
   layout.test.js         Layout tree unit tests (node:test)
   state.test.js          State + connection lifecycle tests (node:test)
   table.test.js          mkio-table pane tests (node:test)
+  pane-filters.test.js   Configured filters, sort, visible: specs and API (node:test)
+  links.test.js          LinkHub and table-to-table linking (node:test)
+  history.test.js        Versioned tables: capabilities, spec, chain logic (node:test)
+  history-pane.test.js   mkio-history pane: versions, diff, blame (node:test)
+  copy.test.js           Clipboard grids: TSV quoting and HTML (node:test)
+  timeparse.test.js      Time detection, parsing, bounds, presets (node:test)
+  icons.test.js          Icon library: every name resolves to an SVG (node:test)
   dialog.test.js         Dialog expression + submission tests (node:test)
   auth.test.js           Authentication module + state lifecycle tests (node:test)
   expressions.test.js    Expression conformance fixtures + mkui wrapper tests (node:test)
   vendor-sync.test.js    lib/expr.js and expr_cases.json match the installed mkio (node:test)
   rich.test.js           Rich text type, mkui function library, clipboard HTML (node:test)
   styles.test.js         mkui.css layout invariants (node:test)
+  tabbar.test.js         Tab bar: drag, reorder, overflow, rename (node:test)
+  tab-focus.test.js      Active tab group and focus routing (node:test)
+  edit-routing.test.js   edit.* actions and shortcuts reach the pane (node:test)
+  pointer-guards.test.js Button/modifier guards on every drag start (node:test)
+  windows-menu.test.js   Windows and layouts menu expansion (node:test)
   layouts.test.js        Saved layouts: format, stores, workspace restore, menu (node:test)
   version.test.js        The four version strings agree (node:test)
   test_cli.py            CLI init/serve tests (unittest)
+  test_control.py        ControlService: push actions to browsers (unittest)
+  test_examples.py       Each example config against its server: the
+                         [mkio.expect] pins, pane services, history
+                         blocks, menu and frame pane ids (unittest)
 ```

{mkui-0.3.0 → mkui-0.3.2}/mkui/__init__.py

@@ -2,7 +2,7 @@
 
 from pathlib import Path
 
-__version__ = "0.3.0"
+__version__ = "0.3.2"
 
 static_dir = Path(__file__).parent / "static"
 """Path to the directory containing mkui's JS, CSS, and example files.

{mkui-0.3.0 → mkui-0.3.2}/mkui/static/examples/mkio-table/config/client.toml

@@ -27,6 +27,24 @@ items = [
   { label = "Order Detail", action = "pane.show", args = "order-detail" },
 ]
 
+[[menubar]]
+label = "Record"
+items = [
+  # The version timeline for whatever All Orders has selected: the chain
+  # as a table, with a diff and a blame view under it. One history pane
+  # per table, re-pointed as the selection moves rather than re-opened.
+  { label = "History…", action = "table.history", args = { pane = "all-orders" } },
+  # `keys` names the record instead, so a menu item can be a deep link.
+  { label = "History of order 1", action = "table.history", args = { pane = "all-orders", keys = ["1"] } },
+  { sep = true },
+  # The steps the All Orders toolbar's Undo and Redo take, on the focused
+  # pane. Deliberately without a shortcut: this writes to shared state.
+  { label = "Undo record", action = "edit.undo" },
+  { label = "Redo record", action = "edit.redo" },
+  { sep = true },
+  { label = "Audit Tape", action = "pane.show", args = "audit-tape" },
+]
+
 [[menubar]]
 label = "View"
 items = [
@@ -106,8 +124,12 @@ protocol = "query"
 # exists in no row, so it must be listed in `columns` explicitly. Derived
 # values are what the table sorts, filters, and copies. SPREAD_BPS is an
 # application function registered in static/app.js.
-columns = ["id", "ts", "side", "symbol", "qty", "price", "notional", "status"]
-labels = { ts = "Time" }
+columns = ["id", "_mkio_version", "ts", "side", "symbol", "qty", "price", "notional", "status"]
+# `_mkio_version` is mkio's own column — the cursor into the record's
+# chain, and the one thing the row itself says about its history. Naming
+# it here is what shows it; mkio's columns are hidden otherwise, and
+# `labels` overrides the default heading ("Version") as for any column.
+labels = { ts = "Time", _mkio_version = "Ver" }
 values = { notional = "ROUND(qty * price, 2)" }
 # Which columns show, in this order. `id` and `price` start hidden — the
 # Columns button at the header's right edge (badge: 2) opens the picker
@@ -115,14 +137,14 @@ values = { notional = "ROUND(qty * price, 2)" }
 # columns still work: `notional` is derived from the hidden
 # `price`, and sorts and filters on hidden columns still apply. Without
 # `visible`, every column shows, including ones added later.
-visible = ["ts", "side", "symbol", "qty", "notional", "status"]
+visible = ["ts", "side", "symbol", "qty", "notional", "status", "_mkio_version"]
 # Column groups categorise the picker (sections with show/hide-the-group
 # toggles; ungrouped columns fall into "Other"). Structure only — `visible`
 # says what shows. With hundreds of columns this is how a user finds the
 # few they want; the config's `visible` is the curated default they can
 # always reset to.
 groups = [
-  { label = "Order",   columns = ["id", "ts", "side", "symbol"] },
+  { label = "Order",   columns = ["id", "_mkio_version", "ts", "side", "symbol"] },
   { label = "Pricing", columns = ["qty", "price", "notional"] },
 ]
 # Mirror the current row into app state; the order-detail pane follows it.
@@ -169,6 +191,26 @@ side = "${BADGE(value, IF(value == 'Buy', 'green', 'red'))}"
 notional = "${NUM(value, digits: 2, group: TRUE)}"
 status = "${ICON(CASE(value == 'filled', 'check', value == 'cancelled', 'close', 'clock'))} ${TITLE(value)}"
 
+# Where this table's record history lives. `versioned = true` on the
+# server's orders table is what records it; mkio advertises no history
+# table and writes no service for one, so this block is the only way the
+# client can know — every name here is a service in server.toml.
+#
+# What it buys: Undo and Redo on the toolbar, stepping the selected orders
+# along their own versions with a confirmation that says what will change;
+# an *As of…* button that shows the table as it stood at a moment,
+# read-only, until *Live* re-subscribes; and Record → History…, the
+# version timeline for the selected order.
+[panes.all-orders.history]
+table    = "orders"          # checked against the server's versioned tables
+key      = ["id"]            # asked of the server when omitted
+versions = "order_versions"  # one record's chain: the history pane
+state    = "order_state"     # where the row sits in it: arms Redo
+feed     = "order_history"   # the audit tape
+undo     = { service = "orders", op = "undo" }
+redo     = { service = "orders", op = "redo" }
+asOf     = "order_as_of"     # the table as it stood at a moment
+
 [[panes.all-orders.buttons]]
 label = "+ New Order"
 enable = { connected = true }
@@ -235,6 +277,17 @@ style = [
 ]
 action = { type = "transaction", service = "orders", op = "cancel", data = { id = "${row.id}" } }
 
+# Undo, Redo and "As of…" arrive on their own — the `history` block above
+# is what puts them there. The version timeline does not: it opens through
+# the `table.history` action, so a table that wants it next to them says
+# so. `unit = "row"` means exactly one record, which is what a history is
+# about; with no `keys` the action takes the pane's current selection.
+[[panes.all-orders.buttons]]
+label = "History"
+unit = "row"
+enable = { connected = true }
+action = { type = "action", name = "table.history", args = { pane = "all-orders" } }
+
 [panes.pending]
 title = "Pending"
 type = "mkio-table"
@@ -374,6 +427,35 @@ labels = { parent_id = "Parent" }
 link.listen = { order_id = "parent_id" }
 link.broadcast = { child_id = "id" }
 
+# Every recorded version of every order, newest first, arriving live as
+# changes land — an ordinary query pane over the history table, with no
+# history block of its own. `_mkio_op`, `_mkio_user` and `_mkio_ref` are
+# mkio's own columns, shown because they are named. The pane is parked (no
+# frame lists it): Record → Audit Tape opens it in a frame of its own.
+[panes.audit-tape]
+title = "Audit Tape"
+type = "mkio-table"
+service = "order_history"
+protocol = "query"
+columns = ["_mkio_ref", "id", "_mkio_version", "_mkio_op", "_mkio_user", "side", "symbol", "qty", "price", "status"]
+labels = { _mkio_ref = "When", _mkio_version = "Ver", id = "Order", _mkio_user = "Changed by" }
+sort = "-_mkio_ref"
+
+[panes.audit-tape.display]
+# The ref is a UTC timestamp; REF_TIME reads it in the browser's zone.
+_mkio_ref  = "${REF_TIME(value, fmt: '%H:%M:%S', tz: 'local')}"
+_mkio_op   = "${BADGE(value, CASE(value == 'insert', 'green', value == 'baseline', 'gray', '#0e639c'))}"
+_mkio_user = "${value ?? MUTED('(system)')}"
+
+# Filtering would narrow what you are looking at; this jumps to the record
+# instead, leaving All Orders showing everything around it. A key its
+# filters hide is reported back rather than revealed, so an order below
+# the pane's `notional` floor says so instead of silently doing nothing.
+[[panes.audit-tape.buttons]]
+label = "Go to order"
+enable = { minSelected = 1, maxSelected = 1 }
+action = { type = "action", name = "table.select", args = { pane = "all-orders", keys = ["${row.id}"] } }
+
 [panes.last-trade]
 title = "Last Trade"
 type = "mkio-table"
@@ -417,11 +499,16 @@ url = "ws://localhost:8080/ws"
 # it too, so the subscription always succeeds.
 control = "_mkui"
 
+# What this app requires of the server it connects to; a mismatch applies
+# `incompatible` below. Below 1.0 semver matching is exact-minor, so the
+# `mkio` pin has to be bumped with every minor release of the library —
+# tests/test_examples.py fails when it goes stale, rather than letting the
+# statusbar quietly read "Wrong server".
 [mkio.expect]
 name = "order-book"
 version = "1.0"
 protocol = "1.0"
-mkio = "0.2"
+mkio = "0.3"
 expr = "1"
 
 [mkio.connected]

mkui-0.3.2/mkui/static/examples/mkio-table/server.toml

@@ -0,0 +1,137 @@
+name = "order-book"
+version = "1.0.0"
+port = 8080
+host = "0.0.0.0"
+db_path = "orders.db"
+# Apply safe schema changes (like adding a column) to an existing orders.db.
+auto_migrate = "safe"
+
+[tables.orders]
+# `ts` is stamped by SQLite in UTC (`YYYY-MM-DD HH:MM:SS`), a format the
+# table recognises as a time, so its filter dropdown offers a date range.
+# `parent_id` nests child orders under a parent (the Order Tree pane): a
+# row whose parent_id is empty is a top-level order.
+columns = { id = "INTEGER PRIMARY KEY AUTOINCREMENT", ts = "TEXT DEFAULT CURRENT_TIMESTAMP", side = "TEXT NOT NULL", symbol = "TEXT NOT NULL", qty = "INTEGER", price = "REAL DEFAULT 0", status = "TEXT DEFAULT 'pending'", parent_id = "INTEGER" }
+# `versioned = true` is the whole switch: mkio numbers every version of
+# every row (`_mkio_version`, 1 on insert and +1 per edit) and records it
+# in a companion `orders__history` table, stamped with the ref, the user,
+# and the service the change came through. `auto_migrate = "safe"` above
+# turns it on for an orders.db that predates this line — the history table
+# is created and every live row recorded as its baseline version.
+versioned = true
+
+# Write endpoint: place and manage orders
+[services.orders]
+protocol = "transaction"
+
+[services.orders.ops]
+new    = [{ table = "orders", op_type = "insert", fields = ["side", "symbol", "qty", "price"] }]
+child  = [{ table = "orders", op_type = "insert", fields = ["side", "symbol", "qty", "price", "parent_id"] }]
+fill   = [{ table = "orders", op_type = "update", key = ["id"], fields = ["status"], defaults = { status = "filled" } }]
+cancel = [{ table = "orders", op_type = "update", key = ["id"], fields = ["status"], defaults = { status = "cancelled" } }]
+# undo/redo take only the key — the values come from the history table —
+# and record no new version, so a step is always reversible. Undoing
+# version 1 removes the row and keeps its versions, so redo can rebuild it.
+undo   = [{ table = "orders", op_type = "undo", key = ["id"] }]
+redo   = [{ table = "orders", op_type = "redo", key = ["id"] }]
+
+# Live table of all orders (mkui subscribes here)
+[services.all_orders]
+protocol = "query"
+primary_table = "orders"
+filterable = ["status", "symbol"]
+
+# Last filled trade per symbol
+[services.last_trade]
+protocol = "subpub"
+primary_table = "orders"
+topic = "symbol"
+where = "status == 'filled'"
+
+[services.last_trade.publish]
+symbol = "symbol"
+side   = "side"
+price  = "price"
+qty    = "qty"
+
+[services.last_trade.defaults]
+symbol = "_mkio_topic"
+
+# ─── Record history ───────────────────────────────────────────────────
+# mkio never advertises a history table and writes no service for one, so
+# these four are the deliberate choice to expose it. Each would take its
+# own `access` rule on a server with authentication enabled — audit
+# visibility is a permission like any other.
+
+# One record's chain, oldest first: what the history pane reads.
+[services.order_versions]
+protocol = "reqrep"
+sql = "SELECT * FROM orders__history WHERE id = :id ORDER BY _mkio_version"
+
+# Where a record sits in its chain: the version its live row is on, and the
+# highest recorded. `current` is null once the row has been undone away.
+# This is what tells the client whether redo has anywhere to go.
+[services.order_state]
+protocol = "reqrep"
+sql = "SELECT (SELECT _mkio_version FROM orders WHERE id = :id) AS current, MAX(_mkio_version) AS top FROM orders__history WHERE id = :id"
+
+# The audit tape: every recorded version, newest first, live as they land.
+# The seeder fills and cancels orders as it runs, so the chains build up
+# on their own.
+[services.order_history]
+protocol = "query"
+primary_table = "orders__history"
+sql = "SELECT * FROM orders__history ORDER BY _mkio_ref DESC"
+filterable = ["id", "symbol", "status", "_mkio_op", "_mkio_user"]
+change_log_size = 10000
+
+# The table as it stood at a moment: for each id, the newest version
+# recorded at or before `as_of`. Refs sort lexicographically, so the cutoff
+# is an ordinary range scan.
+#
+# Reconstructed from recorded versions, which is not quite the same as
+# "what the table showed then": undo and redo move a row's cursor without
+# recording anything, so a row undone at 3pm still reads, as of 2pm, as
+# whatever its newest version by 2pm was.
+[services.order_as_of]
+protocol = "reqrep"
+sql = """
+SELECT h.* FROM orders__history h
+  JOIN (SELECT id, MAX(_mkio_version) AS v
+          FROM orders__history
+         WHERE _mkio_ref <= :as_of
+      GROUP BY id) latest
+    ON h.id = latest.id AND h._mkio_version = latest.v
+ ORDER BY h.id
+"""
+
+# Saved window layouts for mkui's Layout menu: one row per save, the
+# newest being the current layout (`delete` is how the client prunes the
+# history). With no login on this server every save goes to the default
+# history (owner "").
+[tables.mkui_layouts]
+columns = { id = "INTEGER PRIMARY KEY AUTOINCREMENT", app = "TEXT NOT NULL DEFAULT ''", owner = "TEXT NOT NULL DEFAULT ''", saved = "TEXT DEFAULT CURRENT_TIMESTAMP", layout = "TEXT NOT NULL" }
+
+[services.mkui_layouts]
+protocol = "transaction"
+
+[services.mkui_layouts.ops]
+save = [{ table = "mkui_layouts", op_type = "insert", fields = ["app", "owner", "layout"] }]
+delete = [{ table = "mkui_layouts", op_type = "delete", key = ["id"] }]
+
+[services.mkui_layouts_list]
+protocol = "reqrep"
+sql = "SELECT id, saved FROM mkui_layouts WHERE app = :app AND owner = :owner ORDER BY id DESC"
+
+[services.mkui_layouts_get]
+protocol = "reqrep"
+sql = "SELECT id, saved, layout FROM mkui_layouts WHERE id = :id"
+
+# Serve frontend: app at /, mkui framework assets at /mkui/
+[static]
+"/" = "./static"
+"/mkui" = "../../"
+
+# Serve config files
+[config]
+"/config" = "./config"

{mkui-0.3.0 → mkui-0.3.2}/mkui/static/src/core.js

@@ -4,7 +4,7 @@
 // The state store is intentionally tiny: it's a Proxy over a plain object,
 // supports dot-path get/set, and notifies subscribers per path.
 
-export const VERSION = "0.3.0";
+export const VERSION = "0.3.2";
 export function version() { return VERSION; }
 
 import { registerExprFunction, registerExprLibrary, registerExprType, expr } from "./lib/expressions.js";

{mkui-0.3.0 → mkui-0.3.2}/mkui.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mkui
-Version: 0.3.0
+Version: 0.3.2
 Summary: Config-driven, zero-dependency web GUI framework with dockable panes
 Author: Mark Kim
 License-Expression: Apache-2.0
@@ -211,7 +211,7 @@ mkio server and verifies its identity. Connection is two-phase:
     "name": "order-book",
     "version": "1.0",
     "protocol": "1.0",
-    "mkio": "0.2",
+    "mkio": "0.3",
     "expr": "1"
   },
   "connected":    { "status.message": "Connected", "status.background": null },
@@ -227,6 +227,15 @@ to the server's `_mkio` service). When `expect` is absent, the `_mkio`
 query still runs to confirm it is an mkio server and to populate
 `mkio.server.*` state paths (name, version, protocol, mkio).
 
+Semver matching is stricter below 1.0, where the minor number carries the
+breaking changes: `"0.3"` accepts 0.3.x and rejects 0.4.0, so pinning
+`mkio` at a pre-1.0 version means every minor release of the library
+invalidates the pin. A stale pin is quiet — the app connects, the
+`incompatible` map is applied, and the statusbar reads "Wrong server"
+while nothing is wrong with the server. Leave `mkio` out unless the app
+truly depends on the library's version, and pin `name` and `version`,
+which are your own, instead.
+
 The same reply says what the server can do, which lands in
 `mkio.server.services` (service name → protocol),
 `mkio.server.versioned` (the tables whose every change it records — see
@@ -802,7 +811,8 @@ python3 -m http.server 8000
 # http://localhost:8000/examples/library-js/
 ```
 
-The mkio-table example requires [mkio](https://pypi.org/project/mkio/):
+The mkio-table example requires [mkio](https://pypi.org/project/mkio/) 0.3.0 or
+later (its `orders` table is versioned):
 
 ```
 cd mkui/static/examples/mkio-table
@@ -824,6 +834,8 @@ Its `orders` table is `versioned = true`, so mkio records every version of every
 
 **All Orders** broadcasts the selected orders' `id` and `symbol`; the **Child Orders** frame listens for the id on its `parent_id` column and **Pending** for the symbol, so a selection filters both (the chips on each toolbar show and pause the links, and a saved layout keeps them). `python control.py` serves the example in place of `mkio serve` and rewires those links from Python a few seconds after a browser connects. The seeder places child orders under pending parents (and some under other children), so the **Order Tree** tab shows the same orders nested by `parent_id`: expand a parent with its caret, place a child order under the selected row with *+ Child Order*, and try the View menu's expand/collapse actions and alt/option-clicking a filter button for the scope row. The toolbar buttons show both styling forms: the **Pending** tab's Fill and Cancel wear a plain `style` map (green, and black on red in capitals) at all times, while the All Orders Cancel turns red only once a pending order is selected, through a rule conditioned on `enabled`.
 
+The `orders` table is `versioned = true`, so mkio records every version of every row in `orders__history`, and `server.toml` writes the four services that expose it — one record's chain, where a record sits in it, the live tape, and the table as at a moment. **All Orders** names them in a `history` block and shows `_mkio_version` beside the data, which puts *Undo*, *Redo* and *As of…* on its toolbar: filling or cancelling an order moves it to a second version, Undo steps it back with a confirmation that says what will change, and *As of…* shows the book as it stood before the seeder's last few minutes, read-only until *Live* re-subscribes. Undo, Redo and *As of…* arrive with the block; the version timeline does not, so All Orders adds a **History** button of its own beside them — a `table.history` action over one selected record — and Record → History… is the same step from the menubar. Either opens that order's version timeline with its diff and blame views. Record → Audit Tape opens a parked query pane over the history table — every recorded version, newest first, live as they land — whose *Go to order* selects the record in All Orders rather than filtering it (a key All Orders' `status` and `notional` filters hide is reported back rather than revealed). An existing `orders.db` picks all this up on the next start: `auto_migrate = "safe"` creates the history table and records every live row as its baseline version.
+
 ## Project layout
 
 ```
@@ -861,9 +873,10 @@ mkui/                    Python package (pip install mkui)
       standalone-json/   Loaded from a static config
       library-js/        Built imperatively from JS
       mkio-table/        Live table backed by mkio query/subpub services
-                         (config-only derived columns, styling rules, and
-                         enable conditions; static/app.js registers an
-                         expression function and the order-detail pane)
+                         (config-only derived columns, styling rules,
+                         enable conditions, and record history over a
+                         versioned orders table; static/app.js registers
+                         an expression function and the order-detail pane)
       history/           Versioned table: the audit tape, the version
                          timeline with diff and blame, record undo/redo,
                          and the table as at a moment (config only)
@@ -872,13 +885,29 @@ tests/
   layout.test.js         Layout tree unit tests (node:test)
   state.test.js          State + connection lifecycle tests (node:test)
   table.test.js          mkio-table pane tests (node:test)
+  pane-filters.test.js   Configured filters, sort, visible: specs and API (node:test)
+  links.test.js          LinkHub and table-to-table linking (node:test)
+  history.test.js        Versioned tables: capabilities, spec, chain logic (node:test)
+  history-pane.test.js   mkio-history pane: versions, diff, blame (node:test)
+  copy.test.js           Clipboard grids: TSV quoting and HTML (node:test)
+  timeparse.test.js      Time detection, parsing, bounds, presets (node:test)
+  icons.test.js          Icon library: every name resolves to an SVG (node:test)
   dialog.test.js         Dialog expression + submission tests (node:test)
   auth.test.js           Authentication module + state lifecycle tests (node:test)
   expressions.test.js    Expression conformance fixtures + mkui wrapper tests (node:test)
   vendor-sync.test.js    lib/expr.js and expr_cases.json match the installed mkio (node:test)
   rich.test.js           Rich text type, mkui function library, clipboard HTML (node:test)
   styles.test.js         mkui.css layout invariants (node:test)
+  tabbar.test.js         Tab bar: drag, reorder, overflow, rename (node:test)
+  tab-focus.test.js      Active tab group and focus routing (node:test)
+  edit-routing.test.js   edit.* actions and shortcuts reach the pane (node:test)
+  pointer-guards.test.js Button/modifier guards on every drag start (node:test)
+  windows-menu.test.js   Windows and layouts menu expansion (node:test)
   layouts.test.js        Saved layouts: format, stores, workspace restore, menu (node:test)
   version.test.js        The four version strings agree (node:test)
   test_cli.py            CLI init/serve tests (unittest)
+  test_control.py        ControlService: push actions to browsers (unittest)
+  test_examples.py       Each example config against its server: the
+                         [mkio.expect] pins, pane services, history
+                         blocks, menu and frame pane ids (unittest)
 ```

{mkui-0.3.0 → mkui-0.3.2}/mkui.egg-info/SOURCES.txt

@@ -51,4 +51,5 @@ mkui/static/src/widgets/mkui-dialog.js
 mkui/static/src/widgets/text.js
 mkui/static/styles/mkui.css
 tests/test_cli.py
-tests/test_control.py
+tests/test_control.py
+tests/test_examples.py

{mkui-0.3.0 → mkui-0.3.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "mkui"
-version = "0.3.0"
+version = "0.3.2"
 description = "Config-driven, zero-dependency web GUI framework with dockable panes"
 readme = "README.md"
 license = "Apache-2.0"