vega, branch masterSurface runtime projecting Pure views across pixel, terminal, CLI, and web.
http://git.yeowoo.org/vega/atom?h=master2026-10-18T22:54:06ZSize to the module what is the module's (Pure 027's 4f-3a): timers grow to its inputs, the focus marks to its views, the accessibility tree's children to their count; a table shows its first VEGA_COLUMNS (64) columns, Vega's own count2026-10-18T22:54:06Zeunhhunecpition205@gmail.com2026-10-18T22:54:06Zurn:sha1:a2ad1a7a9cd3e608f3fb4e5a694540a9cfef9c69Show views of any value (Pure 027's 4e): a list view is a list or a table (a list state as it is a table of its record's fields), a list in a cell shows how many items it holds, bytes their hex digits, on every surface2026-10-18T21:11:19Zeunhhunecpition205@gmail.com2026-10-18T21:11:19Zurn:sha1:da79f1e2b8d49dabe2290f5d795f8809c8b15c0fSend every input as a message (Pure 027's 4d): keys, text, timers, frames and pointing go to the inputs bound to them; a key's press then its release when a message takes it; vega_frame sends dt 1/60 to the frame input, deferring the save as frames were; a table's pointer is the input pointing at it, sent the item's position; a key's handler found by its input's number2026-10-18T19:54:17Zeunhhunecpition205@gmail.com2026-10-18T19:54:17Zurn:sha1:4d9598e7d0d6d45bf3db9305d365bd2967481bcdchore: add Apache 2.0 license2026-10-10T06:59:27Zeunhhunecpition205@gmail.com2026-10-10T06:59:27Zurn:sha1:991403f164bef7dcf07b053900367a8f0a60ae6cShow an i64 with every digit on every surface2026-09-30T15:33:27Zeunhhunecpition205@gmail.com2026-09-30T15:33:21Zurn:sha1:49e0df31289956aa3fd627f851f8fb2b3e08aa13
vega_text reads an i64 view or column as an integer and prints all of
its digits, so an ID past 2^53 shows as it is on the CLI, the TUI,
speech and the web surface, where a number would round.
Show a bool as true or false, and make the examples' flags bools2026-09-30T14:29:20Zeunhhunecpition205@gmail.com2026-09-30T14:29:20Zurn:sha1:72ecae6b6eb1365e722bd6d45acae8a5ccb74b23
aup and Pure now have a bool (Pure 016): a view or column may be one.
vega_text writes it as true or false, as a string's interpolation does, so
every surface shows the same words: the CLI, the TUI's cells, speech and
the web surface's JSON (a value's text) and page. An app that wants other
words picks them with a conditional (if t.done { "done" } else { "" }).
The flags of the examples are bools: todo's done and urgent, today's done,
the stopwatch's running. vega.when takes the bool as it took the number.
bools checks a bool field and a bool column on the CLI, the TUI, speech
and the web surface: true and false, never 1 and 0.
Say how a value is shown, and what a screen never lets it do2026-09-30T12:19:01Zeunhhunecpition205@gmail.com2026-09-30T12:19:01Zurn:sha1:8fc6f35b30642f3a8ebbd7f5f47b70195c8ffea1Show what would act on a screen as a picture on every surface, and keep a value's bidi within it2026-09-30T12:19:01Zeunhhunecpition205@gmail.com2026-09-30T12:19:01Zurn:sha1:611b54fefc8a02f67cd59041c1795a083ac0bb4c
Speech wrote a value's C1 controls (U+009B is a CSI to some terminals),
DEL, line separators and bidi overrides as they were; the CLI and the
TUI wrote line separators (a pipe's reader may break its line there) and
the controls that turn text around (a terminal then reverses the rest of
its line, other values' cells too); the web page showed controls as they
were and let a label's override reverse its badge. Now every surface
shows controls, DEL, C1 and line and paragraph separators as pictures
(vega_visible); a terminal's cells show embeddings, overrides and
isolates as U+FFFD too (vega_cell); speech says a space for the one and
nothing for the other; the page shows the pictures and isolates each
value, while /screen's JSON keeps values as they are. screen_meaning
checks the CLI, the TUI, speech and the JSON against that rule, and that
nothing a value holds reaches any output as a control; the browser check
sees the page show it.
Add a board two nodes share2026-09-30T05:44:35Zeunhhunecpition205@gmail.com2026-09-30T05:44:35Zurn:sha1:b3c01b3a26a7b5fe60b70739a6fc7b5967e0d9c8
examples/shared-board.aup is the board grown in Pure's research 105:
each node sends a changed card whole to the other (send changed {
..at }) and takes the other's whole when it is the later change
(cards[k] = Card { ..remote }), by its time and then by the node's
name, so both boards end the same whatever order changes come in. The
input the other node sends to is the output's like (message like). A
new field goes in the card and the output alone.
tests/check.py shared_board runs Alice's and Bob's nodes linked both
ways over pure://, sealed, each taking the other as its sender: cards
added, moved and given on either agree; Bob cut off, both give one card
(Bob first, Alice after) and Bob adds one; joined again, both boards
take Alice's and Bob's card.
Say why Pure refused to start or replace the module2026-09-30T04:38:45Zeunhhunecpition205@gmail.com2026-09-30T04:38:45Zurn:sha1:7705831ebdf94186d1513f3e1b8d7d5ab8b3a2c0
pure_app_start and pure_app_replace now say in PureApp.why why they
refused, when they can (sends waiting on an output the module lacks).
Vega printed only the result's number; it prints the reason beside it.