| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
| |
Turns out that the one on Github is ancient and the project was moved
long ago ... which is quite annoying that. No wonder where all the
confusion was coming from.
|
| | |
|
| |
|
|
| |
The plugin now passes the key events to the Wayland clients.
|
| |
|
|
|
|
|
| |
I was initializing the plugin twice, causing hs_init to be called twice
rendering the teardown call to hs_exit useless. Things finally appear to
be working as intended, and it's likely this plugin architecture will
work afterall!
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This is done by passing an interface to the plugin from the harness. The
plugin can then request the harness do some things (such as reload), and
the harness will do that.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
reload.
It turns out I could actually remove the metaload handler from the
plugin interface. As things turn out, when fully unloading the shared
object and reloading it, the Haskell runtime no longer complained. This
makes things much simpler, which is great.
I do wonder if I'm going to run into issues because of this, but I'll
cross that bridge when it's burning.
|
| |
|
|
|
|
| |
Right now nothing interesting is happening, but the new tinywl
implementation is successfully loading a plugin and calling a handler
for 'handle keybinding', which is pretty slick.
|
| | |
|
| |
|
|
|
| |
Add more functions to the plugin interface and write some generators to
generate an interface header file and the plugin's loading code.
|
| | |
|
| |
|