xK - IRC daemon, bot, TUI client and its web frontend

	Commit message (Collapse)	Author	Age	Files	Lines
...
*	xP: separate input buffers	Přemysl Eric Janouch	2022-09-07	1	-8/+15
\|
*	xP: scroll to bottom and focus the input on switch	Přemysl Eric Janouch	2022-09-06	1	-3/+19
\|
*	xP: clean up	Přemysl Eric Janouch	2022-09-06	1	-11/+7
\|
*	xP: indicate connection state	Přemysl Eric Janouch	2022-09-06	1	-7/+23
\|
*	xP: implement tab completion	Přemysl Eric Janouch	2022-09-06	1	-79/+214
\| \| \| \| \| \| \| \|	Currently it only goes for the longest common prefix. Refactor WebSocket handling into an abstraction for our protocol. The Go code generater finally needed fixing.
*	xC/xP: pass timestamps with millisecond precision	Přemysl Eric Janouch	2022-09-06	1	-1/+1
\| \| \| \|	Future-proofing the protocol.
*	xP: convert links to link elements	Přemysl Eric Janouch	2022-09-06	2	-8/+25
\|
*	xC/xP: turn the action asterisk into a rendition	Přemysl Eric Janouch	2022-09-05	2	-5/+9
\|
*	xC/xP: fix colour values, and render them with CSS	Přemysl Eric Janouch	2022-09-05	1	-2/+52
\|
*	Fix up xP's module path, mention the licence	Přemysl Eric Janouch	2022-09-05	2	-1/+4
\|
*	Start X11 and web frontends for xC	Přemysl Eric Janouch	2022-09-05	8	-0/+509
	For this, we needed a wire protocol. After surveying available options, it was decided to implement an XDR-like protocol code generator in portable AWK. It now has two backends, per each of: - xF, the X11 frontend, is in C, and is meant to be the primary user interface in the future. - xP, the web frontend, relies on a protocol proxy written in Go, and is meant for use on-the-go (no pun intended). They are very much work-in-progress proofs of concept right now, and the relay protocol is certain to change.