gnue/common/doc Menus.txt

[James Thompson]

CVSROOT:        /cvsroot/gnue
Module name:    gnue
Changes by:     James Thompson <address@hidden> 02/02/12 20:57:55

Modified files:
        common/doc     : Menus.txt 

Log message:
        more menu notes

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gnue/gnue/common/doc/Menus.txt.diff?tr1=1.2&tr2=1.3&r1=text&r2=text

Patches:
Index: gnue/common/doc/Menus.txt
diff -c gnue/common/doc/Menus.txt:1.2 gnue/common/doc/Menus.txt:1.3
*** gnue/common/doc/Menus.txt:1.2       Fri Feb  1 22:41:05 2002
--- gnue/common/doc/Menus.txt   Tue Feb 12 20:57:55 2002
***************
*** 2,8 ****
  
  GMenu Extends GObj
  
! GMenu objects form a menu tree
  
  all menu items are linked to NAMED triggers
  
--- 2,8 ----
  
  GMenu Extends GObj
  
! GMenu objects does not form a menu tree
  
  all menu items are linked to NAMED triggers
  
***************
*** 12,39 ****
  
  I _think_ we'd need to be able to find menu entries so that <menu> tags
  can somehow place themselves in an existing structure like this
!  find File.Save and put me after it
  
  the entire default system menu and form customizations would be exposed to 
  the trigger system so that we could do menu.file.save.disable =True
  
! If a GMenu contains children it links to a submenu.  
! 
! If a GMenu contains children and had a trigger associated with it the trigger
! will be used to manipulate the submenu selections prior to displaying.
  
  
  If a GMenu contains nothing it's a seperator
  
- 
  GMenu
!   text        - the displayed text on the menu (& before the char that defs 
the alt-hotkey)
!   keymapperEvent - The name of a keymapper event entry that would have the 
same effect as 
!                  - firing 
!   triggerName - the NAMED trigger this menu item should fire upon selection
! 
! 
! 
  
  ---Toolbars---
  
--- 12,43 ----
  
  I _think_ we'd need to be able to find menu entries so that <menu> tags
  can somehow place themselves in an existing structure like this
! find File.Save and put me after it
  
  the entire default system menu and form customizations would be exposed to 
  the trigger system so that we could do menu.file.save.disable =True
  
! If a GMenu is of type dynamic the trigger will be used to 
! manipulate the submenu selections prior to displaying.
  
+ The default menu system for a gnue app would be stored in a file
+ in the gnue/etc area so that it could be customized by the site
  
  If a GMenu contains nothing it's a seperator
  
  GMenu
!   name           - The name of the menu object
!   event          - The comma seperated list of events that this menu item 
should fire
!                  - they will be executed in the order listed
!   trigger        - the name of trigger this menu item should fire upon 
selection
!                  - if the event is type fireTRIGGER
!   type           - normal = a std menu entry
!                  - seperator = visible seperator
!                  - dynamic = the named trigger will be used populate the menu 
structure at runtime 
!   label          - the displayed text on the menu (& before the char that 
defs the alt-hotkey)
!   enabled        - is this item active
!   location       - string containing a . seperated list of object to nest 
into (file.save)
!   leader         - name of menu item this one follows 
  
  ---Toolbars---
  
***************
*** 41,48 ****
  selecting the menu item.  It's basically a graphical symlink to a menu item
  
  If a menu item is disabled the toolbar item is automatically disabled as well
- 
- 
  
  ---Events/bindings---
  
--- 45,50 ----