Re: FVWM: [fvwmorg/fvwm3] msgpack as fvwm <-> modules <-> bindings communicator (#31)
Dominik Vogt <[email protected]>
| Newsgroups | gmane.comp.window-managers.fvwm |
|---|---|
| Message-ID | <[email protected]> |
On Sun, Feb 23, 2020 at 07:37:22PM -0500, Dan Espen wrote: > Thomas Adam <[email protected]> writes: > > > FVWM was written before any formal message parsing libraries existed. Currently, the communication protocol that FVWM uses is a packed structure which is shoved down a pipe, which the receiving end has registered interest in by locking on to various > > messages which are sent. > > > > Other libraries exist to abstract away this message construction, such as msgpack which allows for other binary data to be considered (rather than packing unsigned longs down a pipe, which is how FVWM does this currently). > > > > Another benefit is that other languages have native msgpack bindings, which would allow for agnostic FVWM APIs to be created to allow scripting in any language. This is similar to how neovim does things, for example. Please don't forget a way to just send text from a shell script without having to link with some library. Ciao Dominik ^_^ ^_^ -- Dominik Vogt