aboutsummaryrefslogtreecommitdiffstats
path: root/lib
diff options
context:
space:
mode:
authoreunhhu <[email protected]>2026-09-27 19:37:33 +0100
committereunhhu <[email protected]>2026-09-27 19:37:33 +0100
commit5fe8104744d3e0a48674b1368db6fd104a10bdd4 (patch)
treeed9ea83c6a84a09136f40dc7ff6141968e75faec /lib
parentad3eb77af098f34c1ea8cb50f468a8b75fb7d61c (diff)
downloadvega-5fe8104744d3e0a48674b1368db6fd104a10bdd4.tar.gz
vega-5fe8104744d3e0a48674b1368db6fd104a10bdd4.zip
Show a Pure node's app on its display, as a surface in the node
The vega host builds a second way, as build/vega-surface.so, which pure-serve maps and runs beside its connection threads (pure-serve --surface vega-surface.so -- display ..., Pure's design 010). There the app it draws is a reader of the node's last save, read where it is, and what people type goes to the node's owner: a key press as the key input's event, the typed line as the text input's, each applied and saved with the node's requests. It waits on its input devices and the node's changes descriptor together, leaves timers and signals to the node, and stops with it. The library calls the app model pure-serve exports and links none of its own; it exports pure_surface_run alone. Without --live or --input it takes no input: the node's saves alone draw it. The check gives a node an item over HTTP, then runs the display in the node with recorded keys (an item, Enter, Tab, Space): the last frame is the one vega tui draws for the same state and keys, it came back from the display controller as drawn, and the node's views show both items.
Diffstat (limited to 'lib')
0 files changed, 0 insertions, 0 deletions