On Sat, Oct 05, 2002 at 05:22:55PM +0000, Mikhael Goikhman wrote: > On 05 Oct 2002 12:42:32 -0400, Ben Mathews wrote: > > > > Mikhael Goikhman wrote: > > >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? > > > > I kind of think that calling a taskbar anything other than a taskbar > > might be confusing to anybody not familiar with fvwm, > > I don't think so, does GNOME or KDE have a separate concept of task bar? > They have a concept of a configurable panel, something that we all try to > achieve. > > > but you also have a very good point about having less code to maintain. > > Actually there is one more solution. The goal is to have only one code and > one syntax for one complete feature. But this feature may be embedded in > several modules. I.e. create a library that is used in 2 or more modules. > > But I think that whoever writes such library will come to a conclusion > that it is more clean to have modular setup, like FvwmPanel swallows > FvwmWinList (I use here the ideal names) than to try to embed such big > features like fully featured window list a-la FvwmIconMan or fully > featured button layout a-la FvwmButtons. > > This does not mean other features like time-outed tips/balloons can't be > moved to the library for use in all C modules. > > > Could you post your fvwm2rc file that shows how you got the neat XP > > taskbar with FvwmButtons shown on the screenshot? It looks pretty cool. > > Well, you can't see what it does (it is dynamical) without running it. > To get the configuration, get the fvwm-themes cvs (or browse it online). > You want the files in themes/redmondxp/modules/ directory. Some knowledge > of how the modules component works in fvwm-themes may help too.
Yay! Let's dump yet another module! 8-) FvwmTaskbar is way too difficult to maintain already. A modular setup sounds fine. The FvwmTile/FvwmCascade -> FvwmRearrange way may work too: Replace FvwmTaskBar with a symbolic link to FvwmButtons and add a "--taskbar" option too (note that I'd like to move to GNU style long option names in the future). When FvwmButtons is started in "TaskBar" mode it reads all "*FvwmTaskBar..." config lines and translates them to the proper FvwmButtons config language. The translation may be done by calling a perl script. This is what has to be done: * Add the FvwmButtons taskbar mode code and provide default options to emulate a plain FvwmTaskBar by default. * Write a translation script. This is the tedious part. * Add the features that are missing in FvwmButtons/FvwmIconMan. In the same way, it should be possible to emulate FvwmWinList with FvwmIconMan (FvwmWinList shares a lot of the FvwmTaskBar code). Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- 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]
