"Patrick K." <patrick_at_mail.boxsoft.com> writes:
> Sometime in the late 1900s it was said:
>
> > I agree with #3, but I'm not ready to say that Perl, Python, Scheme, or
> > Tcl is the language. I don't see any of them as being 'configuration'
> > languages. Sucking in menus by doing:
> >
> > %RootMenu = (
> > 'Title' => 'Toys',
> > 'Xterms' => (
> > 'regularterm' => 'xterm',
> >
> > (etc) would be sort of nifty, but does that really belong in a WM? (And
> > I'm beginning to think it's nifty enough that I should play with
> > FvwmPipe or X11::Fvwm and see if I can hack something like that....)
>
>
> Now I don't want to yelled at :) but how about taking
> the approach of HTML tags? What you typed up there got
> me thinking, what if we could have tags for each menu and
> menu items? Like:
>
> <MENU NAME="Root-Menu">
> <MENUITEM NAME="Xterm"
> ACTION="xterm -T $LOGNAME_at_$HOSTNAME">
>
> <SUBMENU NAME="Utils">
> <MENUITEM NAME="Top" ACTION="rxvt -T Top -n Top -e top">
> <MENUITEM NAME="Xload" ACTION="xload -fg green -bg black -hl
red">
> <MENUITEM NAME="Calculator" ACTION="xcalc">
> </SUBMENU>
> <!--
> ! and so on ... -->
> </MENU>
>
> Same with FvwmButtons... you could use the syntax used for
> HTML tables (ie. <TABLE> tag).
>
> Or does this sound totally stupid? :)
I, for one, would say that we would just replace one obscure
configuration language with another obscure configuration language.
How would you create the above on the fly from information found in
the file system?
/tonny
--
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 Tue May 05 1998 - 03:11:37 BST