vega/surfaces, 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:4d9598e7d0d6d45bf3db9305d365bd2967481bcdShow 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.
Show 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.
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.
Keep a key cut across the terminal's reads until it comes whole2026-09-29T17:12:28Zeunhhunecpition205@gmail.com2026-09-29T17:12:28Zurn:sha1:461714a01549841746b721d38441df21f74a4077
handle_input found escape sequences only whole within one read, so an
arrow whose ESC [ came in one read and its A in the next was Escape, [
and A (Pure's review 004, F5); a UTF-8 character cut the same way went
in pieces. A read's bytes are not the terminal's keys: now an escape
sequence, a mouse report or a character cut short waits for the next
read. An escape alone that nothing follows within 100 ms (vim's
ttimeoutlen) is the Escape key; the rest of a key already begun waits up
to a second.
check.py's interactive runs a third session with every key coming a
byte at a time, 50 ms apart, and the arrow's A 150 ms after its ESC [:
the focus moves, as when keys come whole; Vega before this marks the
wrong task done.
Wait for timers on the monotonic clock; events still see the wall clock2026-09-29T17:12:23Zeunhhunecpition205@gmail.com2026-09-29T17:12:23Zurn:sha1:c919b5f81ad6cad55935fa7a22bfda9539dd584f
The terminal, the pixel surfaces and the web page reckoned when a timer
was due on the wall clock: set back, a timer waited until the clock came
again to the tick it had waited for (Pure's review 004). vega_clock is
the monotonic clock; timers are due on it, and a tick sets the time its
event sees from the wall clock (vega_now), as before.
check.py's clock_set_back runs a timer of 20 ms in the terminal with the
wall clock set back an hour 0.2 s in (Pure's build/clock-back.so, an
LD_PRELOAD of clock_gettime): 40 ticks in 0.8 s, where Vega before this
stops at 9. make check passes it --clock-back.
Set type on the pixel surfaces: the grid lays out, the fonts shape2026-09-28T14:52:35Zeunhhunecpition205@gmail.com2026-09-28T14:52:35Zurn:sha1:0b554f2ea62a921e1c8a43ffb24ad75f428af2d6
vega_draw keeps what it wrote as spans (VegaSpan: a row, the columns it
was given, where its cells reached, its text and tone). A span written
where the same pen stopped follows the one before it (a field's name and
value, the help line, the prompt); one written after the pen moved (a
table's column, a list's label, a badge) starts afresh at its column, and
a badge sits flush with its end.
When the first font shapes, the pixels set type: a span and those
following it are one line of text, laid out as one paragraph in the font
stack (bidi and kerning cross the spans; each glyph takes the tone of the
span its character came from), from its column up to the nearest of its
spans' ends and the next span on the row, cut at a grapheme cluster
boundary with an ellipsis if it must be. The prompt gets a text cursor.
--symbols repeats: fonts in order of preference (at most 8); the cells,
when the first font does not shape, also fall back through them.
The check sets a label in one script, alone in its list, and holds it to
what the font that has it sets by itself (vega-symbols paragraph, which
now sizes itself to its text with width 0), pixel for pixel: Latin
kerning, Hangul, Arabic and Devanagari over DejaVu Sans, Noto Sans CJK KR
and FreeSans.