Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

msgpack as fvwm <-> modules <-> bindings communicator #31

Closed
ThomasAdam opened this issue Feb 22, 2020 · 1 comment
Closed

msgpack as fvwm <-> modules <-> bindings communicator #31

ThomasAdam opened this issue Feb 22, 2020 · 1 comment
Assignees
Labels
help wanted Development help required (see `difficulty:*`) type:enhancement Augmenting an existing feature
Milestone

Comments

@ThomasAdam
Copy link
Member

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.

Hence, it would be interesting to:

  • Replace the current FVWM <-> Module messages with msgpack;
  • Expose interfaces for modules to listen on certain events;
@ThomasAdam ThomasAdam added type:enhancement Augmenting an existing feature help wanted Development help required (see `difficulty:*`) labels Feb 22, 2020
@ThomasAdam ThomasAdam self-assigned this Feb 22, 2020
@ThomasAdam ThomasAdam added this to the post-1.0 milestone Feb 22, 2020
@ThomasAdam ThomasAdam modified the milestones: post-1.0, 1.0 Jul 29, 2020
@ThomasAdam
Copy link
Member Author

This has now mostly been completed via FvwmMFL -- will eventually move in to the core.

@ThomasAdam ThomasAdam moved this to Done in FVWM3 Sep 18, 2022
@ThomasAdam ThomasAdam added this to FVWM3 Sep 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Development help required (see `difficulty:*`) type:enhancement Augmenting an existing feature
Projects
Status: Done
Development

No branches or pull requests

1 participant