Charles Hines writes:
>
> It's funny you should bring this up. I was wondering about that
> myself. I don't want to bloat fvwm, so any new things that come up
> I've been suggesting be implemented in modules if at all possible.
>
> I hadn't said anything about this specific instance, because I think
> that the Pixmap buttons addition & the TitleStyle stuff need to be in
> the main executable, but wasn't sure about the Win95 MenuStyle.
> I'd prefer it (Win95 menus) as a module, but it would probably be too
> slow. Unless the module could be kept running constantly instead of
> being run when needed... Perhaps if modules could override built in
> commands (ie Popup and Menu) to send messages to the already running
> modules, then it might be fast enough.
When I was thinking about writing a Start bar for fvwm (a la Win95's
start bar), I thought: `this has got to be a module'. But then I
realized that it would primarily be using (a) Pixmaps from the icons,
and (b) Menus. Using its own menu code would be wasteful, since 99%
of it would be identical with fvwm's menus, and I would hate for it to
have its own pixmaps, when they are in common with fvwm's (unless
somehow, fvwm told the module about the pixmaps).
I still think it should be a module, but I also think the issues
remain. The counter argument is that the start bar is simply a type
of menu just like the pop-ups that exist in fvwm today.
As far as Menu styles, the MenuStyle Win95 was simply based on the
existing MenuStyle Motif, MenuStyle Fvwm. I think that once a core
amount of functionality has been agreed on for fvwm (e.g. title bar &
title buttons, borders, pop-up menus, etc.), then these should be
customizable via Style directives. If the code were written in an OO
programming language, this would be probably easier than it is today,
and it would allow for a cleaner separation of these styles
(i.e. class MacTitleBar : public TitleBar) (but this is just my
opinion :)
On another note, I'm wondering if many of you out there use Xnest for
debugging fvwm. I've found it to be pretty useful when working on
fvwm. For those who aren't acquainted with this program, it's an X-
Server-in-a-window. You then invoke fvwm as `fvwm -display :1' and
you can test the window manager without fear of crashing your main X
Server or disrupting your session.
Best regards,
-Elan
--
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Mon Oct 09 1995 - 09:55:08 BST