vega - Surface runtime projecting Pure views across pixel, terminal, CLI, and web.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Keep Python's bytecode caches out of the repository	eunhhu	2026-09-27	1	-0/+0
\|
*	Give live surfaces a clock and run timers; add a stopwatch	eunhhu	2026-09-26	1	-0/+0
\| \| \| \| \| \| \| \| \| \| \| \| \|	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.
*	Swap a running app's module: --watch and the swap command	eunhhu	2026-09-26	1	-0/+0
	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.