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

	Commit message (Collapse)	Author	Age	Files	Lines
*	Size to the module what is the module's (Pure 027's 4f-3a): timers grow to ↵HEAD master	eunhhu	40 hours	1	-5/+8
\| \| \| \|	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 count
*	Send every input as a message (Pure 027's 4d): keys, text, timers, frames ↵	eunhhu	43 hours	1	-3/+3
\| \| \| \|	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 number
*	Speak AT-SPI2 on the accessibility bus from the display, over Vega's own D-Bus	eunhhu	2026-09-28	1	-0/+806
	vega display --access joins the accessibility bus as AT-SPI2 objects for screen readers such as Orca, with no toolkit, ATK or libdbus: dbus.c speaks the D-Bus wire format (EXTERNAL authentication, headers, aligned bodies, calls, replies, signals). The tree follows what the say surface says: a heading, a label per field, a list box per list whose items know their place and which is selected and focused, tables, the entry, the keys as buttons; answers come from the app when asked, one object has the focus, and focus moves are said as events. Assistive technology can act too: Selection focuses a row, Action presses a key. The live loop now draws only when something changed, so a screen reader's questions no longer cost frames. The check walks the tree with gdbus on a private session bus with at-spi-bus-launcher, and follows the focus through keys, Selection, Action and the events.