On 06 Oct 2002 09:04:35 +0200, Olivier Chapuis wrote: > > On Sun, Oct 06, 2002 at 02:51:36AM +0000, Mikhael Goikhman wrote: > > > > Is anyone interesting in adding the following features to FvwmIconMan: > > > > * a configurable maximal item width (like *FvwmTaskBar: ButtonWidth) > > * tooltips (like *FvwmTaskBar: ShowTips) > > Should be in a lib (some users ask this for FvwmButtons). > > > * a configurable spacing between items > > * a configurable fixed item height (we have no analogue yet) > > One very interesting feature of the TaskBar is that its width is > exactly the screen width whatever the border width (this is even > dynamical). So for me a must is: > > * Do so that FvwmButtons understand % geometries as width%pw x height%ph: > force the geometry of the FvwmButtons window (border width taken in > account) to be ScreenWidth * pw/100 x ScreenHeight * ph/100. This > should be maintained during FvwmButtons life.
Probably extend FScreenParseGeometry to support 100%x5% syntax. > An other minor feature of the taskbar is the asymmetric look of the > relief of the buttons. Users may complaint if this disappear. FvwmIconMan already supports 5 types of relief, adding more would be nice. How about oval 3d borders and small spacing between buttons. :) > Also there is the "..." feature and AutoStick. But I do not like > these two :o) Actually AutoStick may be interesting as a general window feature, but it is really not a showstopper. > Also, it seems to me that it will be difficult to simulate FvwmTaskBar > resizing with a FvwmButtons: StartButton and GoodiesButton have fixed > size as the "WinList" use the full height. Note that I always resize > my TaskBar during a session. Yes, the current table-only center-expand-and-fill layout management of FvwmButtons does not permits this, but it is not very bad as it works now. > About Goodies: Mikhael is FvwmPerl can be used to write a "Proc" modules: > A module which will send (configurable) string and Icon with a configurable > period whenever > - The time change > - The used disk swap space / memory change. > - battery state change. > - Cpu info change. > - mailbox change. > - etc ... > > Maybe there is a "proc" Perl module? Even if such package exists, I don't want users to install anything from CPAN (except for Gtk-Perl, because this is too nice GUI to miss it). I am ready to write FvwmMonitor (or whatever this is to be named) once I figure out the monitoring code for memory/disk/battery/cpu. > > The last feature would enable automatical switching from one row to two > > and more rows when FvwmPanel (i.e. FvwmButtons) is resized. > > > > The next is moving of any-window-autohiding to fvwm or a module. > > Ah yes this is an important feature. It is broken but it works > surprisingly well :o) > > My conclusion. Yes it is a bit stupid to maintain 3 modules for > "window list". I vote for the replacement of the FvwmWinList by > a symlink and a warped config (one "sort" issue here). > For the TaskBar, in the view of the enormous work needed (I do not > want to do it now), I think that we should put the FvwmTaskBar > removal in the 2.8 or 3.0 todo list. If we speak about names and symlinks, probably the new super-windowlist module should have a new name. I may think about: FvwmWinList (not really a new name, but it is the best for me) FvwmWindowList FvwmTaskList FvwmAppList I don't like very much the last two, FvwmWindowList is ok. So maybe as a temporary solution, copy FvwmIconMan to FvwmWindowList and start to clean up FvwmWindowList? Or replace FvwmWinList? > Moreover, I think that FvwmTaskBar is easy to maintain. I am agree > that the code is not terrible. But IconMan code is really terrible! > > So one thing which should be done too is to make a big clean up > of FvwmIconMan code. Yes, it is terrible. I think the multi-manager support may be removed. I don't see a good reason to have it. Just run 2 FvwmIconMan's. 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]
