Closed trvv closed 5 years ago
Good work. I've decided that I'll leave this pull request open, though, until cctl is feature complete. Once that happens it will likely replace custardctl as the main user interface with custard.
What should I continue to add? Should I just make the syntax for it custardctl compliant?
Best case-scenario, cctl could become the drop-in replacement for custardctl, without breaking existing configurations. As for feature completeness, at the very least cctl should implement each of the commands that can be output to the custard socket (see the Wiki page or run custardctl commands with dry
append to the end for socket inputs).
Ideally, it would also implement methods of parsing for specific data (colors with alpha channels in #rrggbbaa format, strings "True" and "False", as well as their lowercase equivalents, evaluating to 1 or 0 respectively, and unsigned integers), as well as helpful error messages that can tell where a user went wrong with an invalid command to cctl.
Parsing for the data can be found at the bottom of src/ipc.c, if need be.
Good to know, I'll start working on proper parsing once I get my own setup decently configured. And currently cctl can execute anything that will be sent to the socket, because it just directly sends inputs to the socket with zero parsing (I know, I know).
@0xfi Any updates on this?
Added cctl as a submodule to custard. Added the installation of cctl to the main
make install
target.