Surface runtime projecting Pure views across pixel, terminal, CLI, and web. http://git.yeowoo.org/vega/atom?h=master 2026-09-27T12:45:31Z 2026-09-27T12:45:31Z eunhhu necpition205@gmail.com 2026-09-27T12:45:31Z urn:sha1:2920e389f624263efe515d9a5f33f6b822efff5e src/ held two parts, the surfaces that show modules to people and the symbol format with its CPU and GPU drawing. As in Pure (design 009), top level directories are now the parts, and the README says what each builds. 2026-09-26T16:58:26Z eunhhu necpition205@gmail.com 2026-09-26T16:58:26Z urn:sha1:b466603358f8fa5a74551a9819fdd54ad124ef0c The terminal and the web page set the time events see to the wall clock and tick an app's timers on time: each round ticks what is due, draws, then waits for input, a frame or the next tick, and a tick is news to every open page at once. Scripts have no clock: time MS sets the time the next events see and tick TIMER ticks, so an app that uses time replays exactly. A module swap reschedules the timers. examples/stopwatch.aup runs on every surface; the checks drive it by script, on a pseudo-terminal by the clock, and on the web page. 2026-09-26T10:54:31Z eunhhu necpition205@gmail.com 2026-09-26T10:54:31Z urn:sha1:8e2b3ffadcf83dba74d58dbf9ee2c57cef5f1ad5 vega tui|web MODULE --watch replaces the running app's module when its file is written again (aup watch writes it); states keep their values by name through pure_app_replace and every web page hears of it. The file is compared by the digest of its bytes, at most five times a second, so a module of the same size written within the same second is not missed; a module that does not load leaves the app as it was and is not tried again. Modules alternate between two slots so a failed load never touches the running one. Scripts get swap MODULE; whether a module runs frames is now a property of the screen. 2026-09-26T10:33:31Z eunhhu necpition205@gmail.com 2026-09-26T10:33:31Z urn:sha1:0d5effd6afe8808296a01db102ca4c247cdcd1af A list may now be filtered (each t in tasks where !t.done), and several filtered lists over one list share one focus: the focus view names an item, so Vega asks Pure which row shows it and highlights it only in the list that holds it; the other lists have no focus (null in the web surface's JSON, and the spoken surface names the item where it is). A click or point on a row points at the item that row shows, and the wheel on a list without the focus focuses the row under it. Pure's rows now take a mutable app. examples/today.aup shows what is open and what is done; its CLI output matches a model over random adds, moves, toggles and points into either list, and the web surface leaves the other list without a focus. 2026-09-26T10:10:44Z eunhhu necpition205@gmail.com 2026-09-26T10:10:44Z urn:sha1:f0a37de5bc9cf924494878e4ab8d3023ddbb27bd The Enter button matches the input beside it, and the key legend shows arrows and short names (↑ ↓ Del PgUp) instead of Pure's key names. 2026-09-26T10:08:29Z eunhhu necpition205@gmail.com 2026-09-26T10:08:29Z urn:sha1:0054ea8452a811f2745d72ce4b7764ea158f1d5f vega web MODULE serves the screen to a browser (127.0.0.1 unless given --listen): one dependency-free page draws the title, fields, lists as listboxes and tables, with tones as colors and the focus highlighted. It asks for the screen as JSON with the rows it can show per list or table, so only those cells are evaluated, scrolled like the TUI around the focus. Keys go as KeyboardEvent.code, which is Pure's key naming already; typed text commits with Enter; a click or the wheel moves the focus through pure_app_point; an event stream tells every open page of each change. Scrolling, key presses and text commits are now shared helpers. The checks drive it against the model (1,200 random steps: title, field, rows, focus, the window of items with badges and tones), check a table's columns and cells, post at random to every example, and in headless Chromium over the DevTools protocol press keys, click a row and type Korean text into the page itself.