15:50:57
##forth
<nmz>
I wonder if there's a TK out there that sets up a socket, and you can bidirectionally receive events from the window and draw to it by issuing commands.
15:51:50
##forth
<nmz>
I guess that's a terminal
15:56:41
##forth
<lispmacs[work]>
this is basically what is going on with a X Server / X Client, right?
15:56:48
##forth
<lispmacs[work]>
but using packets
15:59:19
##forth
<lispmacs[work]>
the sockets are in /tmp/.X11-unix
16:08:58
##forth
<nmz>
No idea
16:10:46
##forth
<nmz>
You are right but since you're running functions in C I didn't think it was doing that
16:15:38
##forth
<lispmacs[work]>
nmz: well, to try to more directly answer your question, I'd say one option you could look at would be send and receiving commands to an intermediary common lisp mcclim program
16:16:16
##forth
<lispmacs[work]>
you could send and receive sexps for the interface actions and events
16:19:12
##forth
<lispmacs[work]>
I know in the past I've had Emacs communicating with a lisp environment over a unix socket, I think it was common lisp
16:19:53
##forth
<lispmacs[work]>
mcclim provides a lispy interface to graphical interfaces
16:20:32
##forth
<veltas>
What problem are you trying to solve?
16:23:45
##forth
<nmz>
Having to use butt ugly C to write a GUI
16:49:38
##forth
<nmz>
Not*
16:50:00
##forth
<nmz>
I was also wondering if you could write a GUI using shellscript and how would you go about doing that
22:52:59
##forth
<xentrac>
nmz: historically that was not a thing you could do
22:53:09
##forth
<xentrac>
13:50 < nmz> I wonder if there's a TK out there that sets up a socket, and you can bidirectionally receive events from the window and draw to it by issuing commands.
22:53:35
##forth
<
xentrac>
this sounds kind of like stdg: https://github.com/calebwin/stdg "stdg" provides #graphics from shell scripts (or anything else that can do text on stdin and stdout) with a simplified PostScript-like command language — but supporting interactivity! Just 1kloc of #Rust. #smallisbeautiful
22:56:50
##forth
<xentrac>
I think that's an approach that has real promise
23:00:00
##forth
<identity>
yeah, "just" 1kloc of rust, + 845 lines of the lockfile
23:07:03
##forth
<xentrac>
haha
23:07:22
##forth
<xentrac>
the kids are not all right