[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openbox
Subject:    [openbox] menu format bummy
From:       smoynes () nexus ! carleton ! ca (smoynes at nexus ! carleton ! ca)
Date:       2003-04-09 17:48:11
Message-ID: 20030409174811.GA18708 () marilyn
[Download RAW message or body]

To bring this in accordance with the Law of Email Subject
Descripionality here's my rough thoughts on menu format bummy:
example:

menu "root" {
     subMenu "terminals";
     subMenu "wooby's k-rad styles";
}

menu "wooby's k-rad styles" style-type;

menu "terminals" {
     execute "aterm";
     execute "aterm -e su";
     spacer;
     subMenu "something defined in someothermenu.menu";
}

include "someothermenu.menu";

Notes:
 - Subject to change. Offer void where prohibited.
 - Menus are registered with names to identify them through the action
 interface. This provides access to all the menus through the
 keyboard.
 - There won't be submenu nesting in the menu format. You can still
 define more than one menu in a file, but each menu NAME {} block is
 flat. This speeds up the refreshing of updated menu files a little
 bit, and makes a few things easier.
 - Menus can also have types, which are provided by menu type plugins.
 - I'll define later all the different actions that are
 possible. There really aren't that many. Most of the interesting ones
 are provided dynamically through plugins.

That is all. I have to go make lotteries now.
s.
-- 
Scott Moynes http://www.icculus.org/openbox/
"Computer science is as much about computers
as astronomy is about telescopes." -- Dijkstra
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://icculus.org/pipermail/openbox/attachments/20030409/3230bb94/attachment.pgp>

[prev in list] [next in list] [prev in thread] [next in thread]