On Sat, Feb 09, 2008 at 11:09:52PM +0000, seventh guardian wrote: > 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.
I believe it's virtually impossible to move menus to a module without removing many features (because of the "some parts that are everywhere". For example, the menu code needs to know the layout of the decorations. Of course the module interface *can* be extended to provide all the menu specific information, but why bother? The only real additional complexity caused by the menu code being a part of the core is that fvwm needs to know that it opened menu windows itself (in case of tear off menus) so it doesn't kill itself. Ciao Dominik ^_^ ^_^ -- Dominik Vogt
