@morgant I'm glad you like them and find those tools inspiring! I'd love to know what they inspired you into... (is it the MLVWM confirmation dialog?)
XFiles controlker script uses xmessage by default, but you can disable it.I personally do not like xmesage. I have tried to use a XTerm window before as a confirmation dialog, so the user can type Y/N and press Enter; but that's not mouse-friendly.
@seninha Certainly a little inspiration for keeping `mlvwm-message`/`mlvwm-alert`/`mlvwm-confirm` dead-simple.
Beyond that, one thing that frustrates me about #MLVWM, and the ancient version of #FVWM it was forked from, is that menu configurations are static. I like your implementations of #xmenu & #pmenu piping menu definitions around dynamically.
I'll likely add a 'DynamicMenu' command, or something like that, which provides similar functionality... (1/n)
@seninha I prefer not to run a full DE (desktop environment), so I don't want to require anything of the sort for #MLVWM. That said, if I add functionality for dynamic menu definitions, I could evetually write a daemon that talks to applications via DBus and asks them for their menus and menu options.
There are a few solutions that already implement such functionality. That would be _soooooo_ much easier than hard-coding them, as I currently have to do! (2/n)
@thomasadam @seninha Thanks, that reminds me: one of the things on my #MLVWM #ToDo list is to review the `Menu` command implementation to see if multiple with the same name append, replace, or fail.
I also just noticed #FVWM’s `PipeRead`, which would solve the problem for Menus and more!
https://man.openbsd.org/fvwm#PipeRead
Though MLVWM doesn’t yet support `Read` within `Menu`.
@thomasadam @seninha One of the things I find funny in #MLVWM is that `Menu` supports check marks and such, which don’t seem useful in non-dynamic menus.
I should check in with Takashi Hasegawa again and see if he has any insights & stories.
Morgan Aldridge
Lucas de Sena
Thomas Adam