aboutsummaryrefslogtreecommitdiff
path: root/xP/public/xP.css
Commit message (Collapse)AuthorAgeFilesLines
* xC/xP: mark highlights and buffer activityPřemysl Eric Janouch2022-09-081-1/+12
| | | | And more or less finalize out the protocol for this use case.
* xP: resolve various issues, mostly in stylingPřemysl Eric Janouch2022-09-071-9/+38
|
* xP: implement buffer line leakagePřemysl Eric Janouch2022-09-071-0/+3
| | | | Rather than on redisplay, these get cleared on reconnect.
* xP: support showing buffer logsPřemysl Eric Janouch2022-09-071-0/+10
|
* xP: convert links to link elementsPřemysl Eric Janouch2022-09-061-5/+5
|
* xC/xP: turn the action asterisk into a renditionPřemysl Eric Janouch2022-09-051-0/+3
|
* Start X11 and web frontends for xCPřemysl Eric Janouch2022-09-051-0/+109
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.