Re: FVWM: Writing a module?

In case there is interest, in the end I wrote the utility in
python/gtk, under the name xtm (x-input-mapper). In the README.md I
describe how to create fvwm2 mappings for it.

See:

https://github.com/dov/x-tablet-mapper

Regards,

On Tue, Nov 28, 2023 at 9:29=E2=80=AFAM Dov Grobgeld <[email protected]=
m> wrote:
>
> Thanks for the tip! I thought that if writing a module was easy, it
> would be an easy way to better blend in with my fvwm theme. So I'll
> probably write in (python) gtk, which was actually my original plan.
>
> Regards,
>
> On Mon, Nov 27, 2023 at 10:58=E2=80=AFPM Jaimos Skriletz
> <[email protected]> wrote:
> >
> > On Mon, Nov 27, 2023 at 1:48=E2=80=AFPM Dov Grobgeld <dov.grobgeld@gmai=
l.com> wrote:
> >>
> >> Hello,
> >>
> >> I would like some guidance on whether the following idea makes sense t=
o do as a fvwm module.
> >>
> >> My question is especially if it makes sense to write 4 as a fvwm modul=
e? What's  a good starting point? Also, once I have a written a module, how=
 would I send it messages to update the visually shown rectangle mapping?
> >
> >
> > I initially don't see anything that would require you to write this as =
a fvwm module. You really aren't using information from fvwm at all (about =
windows, and their state and location).  It will probably be far easier to =
just write a stand alone app using some predefined toolkit (such as tk, gtk=
, etc) to draw the rectangles for you. You could swallow this into FvwmButt=
ons if you wanted it to be part of a panel.
> >
> > For updates, you could set your app up to listen to a socket so you can=
 just send it updated info when you update the tablets mapping.
> >
> > If you really want to go the module route, you could start here.
> >
> > https://www.fvwm.org/Archive/ModuleInterface/
> >
> > jaimos