Edward Langley
a913390322
Three tickets on one subject: paging.
improvise-rw6l — clicking a page chip opens a menu of that axis's items, with
a down-arrow saying so. Almost nothing had to be derived: `PageAxis::items` was
already projected and `ModelCommand::SetPageSelection` was already on the wire.
The one gap was that `RenderPageAxis` dropped the names, keeping the position
and count improvise-p1ym needed for `[`/`]`. `items` is relayed INSIDE `cycle`
rather than beside it, so there is one predicate and not two: a Filter axis has
no cycle, therefore no arrow, no menu, no items, and composes nothing if a click
reaches it — all four off `PageAxis::cycle`, the one home of gotcha 27's split.
improvise-771e — the browser tile bar said "Quarter Pag". `short_label` is three
characters so the TUI aligns in a fixed-width terminal (gotcha 26); a browser has
no column to fit. `render.rs` asks `plain_label` instead; `short_label` is
untouched. Note what pinned the truncation was `harness/tests/drill.spec.js`,
not `tests/grid_frame_agreement.rs`, which does not mention the tile bar.
improvise-wiew — `[`/`]` move from Normal onto a new `document_keymap` between
the global and the modes whose subject IS the document (Normal, the three
panels, TileSelect; RecordsNormal through Normal). Help and the import wizard
take the global directly. Per the user's ruling: an overlay has a subject of its
own, and these are the first shared keys that MUTATE the document — under the
help overlay that is an invisible change to the grid it is covering.
Boundary crossings to flag, both outside the brief's stated write scope and
neither a wire change:
- `resolve.rs` gains `Click::PageItem` and `lib.rs` a `click_page_item`
binding. Composing the command anywhere else would put a derivation in the
page, which design-principles §5 forbids; `Command`/`ModelCommand` are
untouched.
- `improvise-command/src/command/keymap.rs` gains three tests. The two
existing guards were the mechanism that forced the wiew argument, so they
had to be answered where they live.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FC2jVn8Au7E9JPkw6bwXXH
137 lines
5.8 KiB
HTML
137 lines
5.8 KiB
HTML
<!doctype html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta charset="utf-8" />
|
|
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
|
<title>improvise</title>
|
|
<link rel="stylesheet" href="./style.css" />
|
|
</head>
|
|
<body>
|
|
<!--
|
|
The browser shell (improvise-cr3, improvise-djm).
|
|
|
|
Deliberately four elements and no framework. Everything that could be
|
|
*wrong* — what a cell is, whether it may be typed into, where the
|
|
selection sits, how the category tree flattens — is decided in Rust and
|
|
arrives already decided (see `render.rs`). This page paints it.
|
|
|
|
Build both wasm bundles first:
|
|
|
|
./web/build.sh
|
|
|
|
then serve this directory over http (a module script will not load from
|
|
file://):
|
|
|
|
python3 -m http.server 8080 --directory web
|
|
|
|
That is the whole standalone deployment: the document lives in an
|
|
in-page Web Worker and persists to this browser's private storage.
|
|
?doc= and ?seed= name the document and the file it is first seeded from.
|
|
|
|
To talk to a separate `improvise-ws-server` process instead — which is
|
|
how a document open in the TUI is shared — pass ?ws=host:port; the
|
|
scheme defaults to wss:// on https and ws:// on http.
|
|
-->
|
|
<header>
|
|
<h1>improvise</h1>
|
|
<!--
|
|
What this page IS: web/assemble.sh rewrites the text below to the tag
|
|
or commit it assembled from (improvise-oujb). It sits with the name
|
|
because the bar's order starts at "what this is", and a tree served
|
|
straight out of web/ was never assembled and honestly says so.
|
|
-->
|
|
<span title="Build this page was assembled from" id="build-version">unstamped</span>
|
|
<span id="doc-name"></span>
|
|
<span id="view-name"></span>
|
|
<span id="mode"></span>
|
|
<span id="hint"></span>
|
|
<span id="status" role="status"></span>
|
|
</header>
|
|
|
|
<!--
|
|
This page is the *client* half and nothing else: it holds no model. What
|
|
it now has is a peer it can always reach — a Web Worker in this same tab
|
|
hosting the whole App over OPFS (improvise-9x6, improvise-djm) — so a
|
|
copy served from a static host, GitHub Pages included, is a working
|
|
application rather than a client with nowhere to connect.
|
|
|
|
The notice below stays static HTML rather than something app.js decides,
|
|
for the same reason as before: it is true on every load in either mode,
|
|
and a page that cannot reach its peer cannot be trusted to explain why.
|
|
What the peer is actually *doing* — starting, connected, unreachable,
|
|
gone — is live, and app.js writes it to #status.
|
|
|
|
It is a <details>, so the collapsing is the BROWSER's — keyboard
|
|
operable, and correct with app.js absent or still loading. The only
|
|
thing app.js adds is remembering the answer; the one line every visitor
|
|
needs is the <summary>, which never collapses.
|
|
-->
|
|
<details id="backend-notice">
|
|
<summary>
|
|
<span class="notice-lede"
|
|
>Everything here runs in this tab — the document lives in a Web
|
|
Worker and is saved to this browser's private storage, so edits
|
|
survive a reload and never leave the machine.</span
|
|
>
|
|
<span class="notice-toggle" aria-hidden="true"></span>
|
|
</summary>
|
|
<div class="notice-body">
|
|
<p>
|
|
Load a different document with <code>?doc=name.improv</code>, seeded
|
|
from <code>?seed=url</code>. To open a document hosted by a separate
|
|
process instead, run
|
|
<code>improvise-ws-server model.improv --port 8787</code> and reload
|
|
with <code>?ws=host:port</code>.
|
|
</p>
|
|
<p>
|
|
<strong>The scheme defaults to <code>wss://</code></strong>, because
|
|
this page is served over https and an https origin refuses a
|
|
<code>ws://</code> address as mixed content. Note that
|
|
<code>improvise-ws-server</code> speaks plain <code>ws://</code>
|
|
only, so reaching it from <em>this</em> page means terminating TLS in
|
|
front of it with a reverse proxy or a tunnel — the README has a
|
|
worked Caddy example. Served over <code>http://localhost</code> the
|
|
same page defaults to <code>ws://</code> and pairs with it directly,
|
|
with nothing in between; that is the case the pairing is really for.
|
|
Sharing a document is what the server is for — not running one is
|
|
what everything above is for.
|
|
</p>
|
|
</div>
|
|
</details>
|
|
|
|
<div id="tiles" aria-label="Tiles"></div>
|
|
|
|
<!--
|
|
The page bar: which item each Page or Filter category is fixed to. The
|
|
TUI draws it inside the grid's border; here it is a line of its own,
|
|
above #grid, so it is not charged to the grid's own frame cost.
|
|
-->
|
|
<div id="pages" aria-label="Page axes" hidden></div>
|
|
|
|
<!--
|
|
The page menu (improvise-rw6l). It lives OUTSIDE #pages because that
|
|
element's children are replaced on every repaint, and a menu rebuilt
|
|
under the pointer is a menu that closes itself.
|
|
-->
|
|
<div id="page-menu" role="listbox" aria-label="Page items" hidden></div>
|
|
|
|
<main>
|
|
<aside id="categories" aria-label="Categories"></aside>
|
|
<aside id="formulas" aria-label="Formulas" hidden></aside>
|
|
<aside id="views" aria-label="Views" hidden></aside>
|
|
<div id="grid" tabindex="0" aria-label="Grid"></div>
|
|
</main>
|
|
|
|
<!--
|
|
The bottom bar. The TUI draws the minibuffer INSTEAD of the status line;
|
|
here it is a line of its own, because #status also carries the transport's
|
|
own failures and a repaint must not erase one (gotcha 48).
|
|
-->
|
|
<div id="minibuffer" role="status" hidden></div>
|
|
|
|
<div id="help" role="dialog" aria-label="Help" hidden></div>
|
|
|
|
<script type="module" src="./app.js"></script>
|
|
</body>
|
|
</html>
|