Hello,

I've been "diving" in fvwm core code for the last days trying to get
argb visuals to work. One thing I've noticed is that while the menu
code is mostly separated from the rest of the code, some parts of it
are still everywhere.

IMHO it makes sense to have the menus separated, as they are not a
window manager feature. They are not even required if the user doesn't
want them. So it makes sense to have them as a module.

I believe it should be easy to keep current configs working, and the
compatibility code could be stripped off on future versions of fvwm.

Cheers,
  Renato

Reply via email to