I wanted to write this before FvwTaskBar patch was applied, but realized that 1) many use FvwmTaskBar, 2) I myself have no time to implement what I suggest fully. Still maybe others agree with me.
Having 2 modules implementing the same is twice (if no more) work for maintainance. FvwmButtons and FvwmIconMan already have all features that users want to see in FvwmTaskBar. And vice versa FvwmTaskBar currently has several features that FvwmIconMan users want to see. Generally, every new or old feature should be duplicated. I have several thoughs about a smooth transition from FvwmTaskBar to FvwmButtons with swallowed FvwmIconMan. I think that having only one module for layout (currently FvwmButtons, but the name may be changed to FvwmPanel) is what we need and having only one module managing window list (currently FvwmIconMan, but the better name would be FvwmWinList) is what we need. The idea may be this. We stop adding any features to other modules and only extend FvwmButtons and FvwmIconMan. We then replace FvwmTaskBar with a module that only converts its legacy configuration to FvwmButtons and FvwmIconMan configurations (using aliases like FvwmButtons-FvwmTaskBar and FvwmIconMan-FvwmTaskBar) and starts these modules. In the future we encourage users to use only these 2 modules for creating their panels. Suzanne, Ben, Olivier and other FvmwTaskBar lovers, is there a chance you agree with such arrangement? Would not having one powerful FvwmPanel and one or more "applets" to be optionally swallowed be a better solution? Regards, Mikhael. -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
