On 17 Mar 2002 17:47:27 -0500, Daniel Henninger wrote: > > My only other suggestion was going to be a completely different menu > style of: > > StartMenu "AppMenu" ( SidePic "ninja.xpm", SideColor blue ) > Title "Application Menu" > Separator ( Height 6, Color red, Lines 2 ) > Item "Corporate Time" ( Greyed ) Exec /usr/local/bin/ctime & > Item "Ninja" Exec /usr/local/bin/ninja > Item "Crazy" ( Greyed ) > + Exec /usr/bin/crazy > Item "Whee" Exec /usr/bin/whee & > Item "Foo" > + ( Greyed ) > + Exec /bin/foo > Separator ( Height 1, Color lightblue, Lines 1 ) > Item "Logout" Quit > EndMenu > > Where + was simply a "continue the previous line" so you could split > things up.
This can't work with the current command philosophy. There are no multiline commands, all commands are executed immediately one by one. There are many reasons for this. But I will only list some problems with the sample above. Suppose a user forgot one EndMenu or one StartMenu. Or added some commands inside a menu definition (it is possible now). What to do? Ignore the menu definition? Ignore the non menu lines until the end of file? Close EndMenu automatically? But if this can be done automatically, why EndMenu is needed? Moreover. Currently it is pretty possible to add a function definition in a menu action and a menu definition in a function: AddToFunc func1 I AddToMenu menu1 "some label" AddToFunc func2 I Beep Try to think how to do this using StartMenu/EndMenu StartFunc/EndFunc and what kind of parser (using lex/yacc?) should be implemented. :) 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]
