I've been prototyping a new splitting mode, and that lead me to think about these questions:
-
Are you open to adding more modes to the project?
I understand that this could be a huge overhead as a maintainer, since contributors can come up with all sorts of quirky modes. Reviewing and ensuring relevance to the userbase could be daunting.
-
Are you open to adding a "scripted" sort of mode? Something like:
- the user writes callbacks that form the interface to a mode (i.e.
*_mode_{enter,split,render,etc.})
- these callbacks are called by
wl-kbptr's scripted mode
- callbacks could be written in Lua? Or dynamically loaded from a shared object?
Again, I get that this is challenging, because it entails exposing an interface to external code (and thus keeping it stable).
No pressure though :) wl-kbptr is a pretty neat codebase to hack on, and I found it pretty straightforward to adapt an existing mode to suit my preferences. But I thought I should ask anyways: if either of the above is within your scope and reviewing bandwidth, I would be glad to contribute it.
Cheers!
EDIT: regarding (2), it would probably be a much better idea to define a new interface just for the external code, rather than expose the existing struct mode_interface
I've been prototyping a new splitting mode, and that lead me to think about these questions:
Are you open to adding more modes to the project?
I understand that this could be a huge overhead as a maintainer, since contributors can come up with all sorts of quirky modes. Reviewing and ensuring relevance to the userbase could be daunting.
Are you open to adding a "scripted" sort of mode? Something like:
*_mode_{enter,split,render,etc.})wl-kbptr's scripted modeAgain, I get that this is challenging, because it entails exposing an interface to external code (and thus keeping it stable).
No pressure though :)
wl-kbptris a pretty neat codebase to hack on, and I found it pretty straightforward to adapt an existing mode to suit my preferences. But I thought I should ask anyways: if either of the above is within your scope and reviewing bandwidth, I would be glad to contribute it.Cheers!
EDIT: regarding (2), it would probably be a much better idea to define a new interface just for the external code, rather than expose the existing
struct mode_interface