aboutsummaryrefslogtreecommitdiff
path: root/xP
Commit message (Collapse)AuthorAgeFilesLines
...
* xP: separate input buffersPřemysl Eric Janouch2022-09-071-8/+15
|
* xP: scroll to bottom and focus the input on switchPřemysl Eric Janouch2022-09-061-3/+19
|
* xP: clean upPřemysl Eric Janouch2022-09-061-11/+7
|
* xP: indicate connection statePřemysl Eric Janouch2022-09-061-7/+23
|
* xP: implement tab completionPřemysl Eric Janouch2022-09-061-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 precisionPřemysl Eric Janouch2022-09-061-1/+1
| | | | Future-proofing the protocol.
* xP: convert links to link elementsPřemysl Eric Janouch2022-09-062-8/+25
|
* xC/xP: turn the action asterisk into a renditionPřemysl Eric Janouch2022-09-052-5/+9
|
* xC/xP: fix colour values, and render them with CSSPřemysl Eric Janouch2022-09-051-2/+52
|
* Fix up xP's module path, mention the licencePřemysl Eric Janouch2022-09-052-1/+4
|
* Start X11 and web frontends for xCPřemysl Eric Janouch2022-09-058-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.