Re: (Was: FVWM: Fvwm 2 next release)

From: Kai Grossjohann <grossjoh_at_charly.informatik.uni-dortmund.de>
Date: 12 Apr 1996 17:14:29 +0200

>>>>> On Fri, 12 Apr 1996 08:33:38 -0600 (MDT), "Michael J. Carter"
>>>>> <mcarter_at_lanl.gov> said:

>>>>> "Charles" == Charles Hines <chuck_hines_at_VNET.IBM.COM> writes:

  Charles> the infamous Great Style Flag Rewrite.

  Michael> Will this add functionality or simply reimplement the
  Michael> present features???

Per se, it won't add anything new, but it is the base needed to
implement more per-window stuff. For example, it is currently
impossible to specify per-window autoraise (FvwmAuto{,Raise} is an
all-or-nothing kind of thing); after TGSFR it will be rather easy to
add, I gather.

  Michael> One of our sysadmins can't tear himself from tvtwm because
  Michael> of it's ability to assign window border, icon and menu
  Michael> entry colors on a per-menu-item basis.

He's got a menu where the first item is blue and the second is red?
Well... de gustibus non disputandem.

  Michael> The other feature he's after is tvtwm's dynamic menus...

What are dynamic menus? Haven't used tvtwm in a couple of years now,
but I don't see why one shouldn't be able to do useful stuff with
functions.

With Fvwm you can put menu definitions in a file, then read that file
at run time to have these take effect. So, you write a shell script
that does:

    echo AddToMenu Bla \"Item\" Exec xterm >> ~/.fvwm/foo-menu

And you can do

    Read ~/.fvwm/foo-menu

from a menu or a keybinding. This seems to be Turing-complete. Can
tvtwm do better than this?

kai
--
There ain't no cure for the summertime blues.
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
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 Fri Apr 12 1996 - 10:11:58 BST

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:37:58 BST