<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vega/examples/stopwatch.aup, branch master</title>
<subtitle>Surface runtime projecting Pure views across pixel, terminal, CLI, and web.
</subtitle>
<id>http://git.yeowoo.org/vega/atom?h=master</id>
<link rel='self' href='http://git.yeowoo.org/vega/atom?h=master'/>
<link rel='alternate' type='text/html' href='http://git.yeowoo.org/vega/'/>
<updated>2026-09-30T14:29:20Z</updated>
<entry>
<title>Show a bool as true or false, and make the examples' flags bools</title>
<updated>2026-09-30T14:29:20Z</updated>
<author>
<name>eunhhu</name>
<email>necpition205@gmail.com</email>
</author>
<published>2026-09-30T14:29:20Z</published>
<link rel='alternate' type='text/html' href='http://git.yeowoo.org/vega/commit/?id=72ecae6b6eb1365e722bd6d45acae8a5ccb74b23'/>
<id>urn:sha1:72ecae6b6eb1365e722bd6d45acae8a5ccb74b23</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Give live surfaces a clock and run timers; add a stopwatch</title>
<updated>2026-09-26T16:58:26Z</updated>
<author>
<name>eunhhu</name>
<email>necpition205@gmail.com</email>
</author>
<published>2026-09-26T16:58:26Z</published>
<link rel='alternate' type='text/html' href='http://git.yeowoo.org/vega/commit/?id=b466603358f8fa5a74551a9819fdd54ad124ef0c'/>
<id>urn:sha1:b466603358f8fa5a74551a9819fdd54ad124ef0c</id>
<content type='text'>
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.

</content>
</entry>
</feed>
