On Wed, Oct 30, 2002 at 09:08:27AM +0000, Mikhael Goikhman wrote: > On 29 Oct 2002 22:32:53 -0800, [EMAIL PROTECTED] wrote: > > > > On Tue, Oct 29, 2002 at 12:25:56PM +0000, Mikhael Goikhman wrote: > > > [...] > > > > > > How about renaming this module to something that is more intuitive? > > > I may think about FvwmProxyWindows, FvwmWindowMarks, FvwmIndicators. > > > I am sure you may find a better name. > > > > If its confusing that it might, say, route packets to other > > managers or be used to visualize your firewall, I can be flexible. > > This was my first association. I also thought about something similar to > FvwmCommandS. I needed to look at the code and configuration to figure out > what it really does. > > > To be consistant with existing modules, how about FvwmWinProxy? > > Just so I don't have to change the dozens of instances of the > > word 'proxy' in the source. > > FvwmWinProxy is fine with me although I myself would probably use plural. > > Actually, the only module to be consistent with (FvwmWinList) together > with FvwmIconMan and FvwmTaskBar is likely to be replaced/united in the > long run. I suggested either FvwmWindowList (better, because this is a > new name) or FvwmWinList for such super window list modules. > > So, please throw the final name.
Some suggestions: FvwmMiniWindows FvwmLabels FvwmWinBanners Bye Dominik ^_^ ^_^ -- 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]
