aboutsummaryrefslogtreecommitdiff
path: root/xC-gen-proto-go.awk
Commit message (Collapse)AuthorAgeFilesLines
* Move protocol code generators to libertyPřemysl Eric Janouch2022-09-301-538/+0
| | | | This part of the project is now more or less stable.
* Clean up protocol code generatorsPřemysl Eric Janouch2022-09-301-34/+53
|
* xP: improve comments in protocol code generatorPřemysl Eric Janouch2022-09-151-5/+5
|
* xP: further optimize JSON marshallingPřemysl Eric Janouch2022-09-151-20/+27
|
* xP: fix log JSON serializationPřemysl Eric Janouch2022-09-151-0/+9
|
* xP: generate our own JSON marshallersPřemysl Eric Janouch2022-09-141-5/+62
| | | | | For non-trivial types, which are expensive to serialize with encoding/json's struct reflection.
* xC-gen-proto: reduce enums to single bytesPřemysl Eric Janouch2022-09-101-7/+5
| | | | That's already way more than we can possibly use.
* xP: implement tab completionPřemysl Eric Janouch2022-09-061-1/+2
| | | | | | | | 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.
* Start X11 and web frontends for xCPřemysl Eric Janouch2022-09-051-0/+447
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.