Recent changes to Menu reference

Menu reference modified by Thomas Luebking

Thomas Luebking — Sat, 20 Apr 2013 18:48:04 -0000

--- v5
+++ v6
@@ -5,7 +5,7 @@

     
         
-            []
+            []
             []
             []
         
@@ -18,15 +18,17 @@

 It's attributes can be either
 * **menu**
-
A reference to another xml file, following this very same structure (i.e. "inherit" another file)
-The path is relative to ~/.kde/share/apps/be.shell/ and an ".xml" suffix is applied automatically, eg. "subpath/submenu" turns to "~/.kde/share/apps/be.shell/subpath/submenu.xml"
+A reference to another xml file, following this very same structure (i.e. "inherit" another file)
The path is relative to ~/.kde/share/apps/be.shell/ and an ".xml" suffix is applied automatically, eg. "subpath/submenu" turns to "~/.kde/share/apps/be.shell/subpath/submenu.xml"

 * **label**
 A label for the popup entry, defined in the following subnodes
 * **windowlist**
-Adds a window list, generated by BE::Shell
+Adds a window list, generated by BE::Shell

 * **BE::Config**
 Adds the BE::Shell config menu (the one you get by rightclicking on the Desktop)
-
+* **preExec** ("menu=subpath/submenu" only!)
+An executable to be run before the menu pops up (usually a script writing the menu definition) **Needs to be an absolute path**, no bash aliases either

+* **preExecTimeout** (defaults to "250", "menu=subpath/submenu" only!)
+The maximum amount of time in ms to allow the preExec command to block the GUI before it's cancelled.


 The actual popup menu entries can be subnodes
 * *\*

WikiPage Menu reference modified by Thomas Luebking

Thomas Luebking — Tue, 03 Jul 2012 18:11:54 -0000

--- v4
+++ v5
@@ -30,11 +30,12 @@
 
 The actual popup menu entries can be subnodes
 * *\*
-
Yet another submenu
+Yet another submenu
+
 * *\*
-
An active item, that actually triggers sth., can also be put directly into the  node, though this is rather uncommon.
+An active item, that actually triggers sth., can also be put directly into the \ node, though this is rather uncommon.
 
-It's attributes can be either
+    It's attributes can be either
     * **label**
     
A label for the entry, overriding that in any given service
     * **icon**
@@ -43,7 +44,7 @@
     
 A dbus call, separate by semicolons.
     \;\;\;\;\\[;\\[;\\[;...\]\]\]
     * **exec**
-    
either a service name or an executable, or a path, or ... basically anything you can type into krunner or konqueror, ie. "gg:KDE" will google for KDE!
+    either a service name or an executable, or a path, or ... basically anything you can type into krunner or konqueror, ie. "gg:KDE" will google for KDE!
     If this is a service, it's label and icon can be overridden by the related attributes
 
 * **\**

WikiPage Menu reference modified by Thomas Luebking

Thomas Luebking — Tue, 03 Jul 2012 18:09:38 -0000

--- v3
+++ v4
@@ -13,8 +13,8 @@
 
 It's nearly the same code as in XBar (which was ported from BE::Shell)
 
-The first node is always ""
-To add a menu entry, add a "" node, this will add a popup menu.
+The first node is always "\"
+To add a menu entry, add a "\" node, this will add a popup menu.
 
 It's attributes can be either
 * **menu**
@@ -29,9 +29,9 @@
 
 
 The actual popup menu entries can be subnodes
-* **
+* *\*
 
Yet another submenu
-* **
+* *\*
 
An active item, that actually triggers sth., can also be put directly into the  node, though this is rather uncommon.
 
 It's attributes can be either
@@ -41,13 +41,13 @@
     
 An icon for the entry, overriding that in any given service
     * **dbus**
     
 A dbus call, separate by semicolons.
-    ;;;;[;[;[;...]]]
+    \;\;\;\;\\[;\\[;\\[;...\]\]\]
     * **exec**
     
either a service name or an executable, or a path, or ... basically anything you can type into krunner or konqueror, ie. "gg:KDE" will google for KDE!
     If this is a service, it's label and icon can be overridden by the related attributes
 
-* ****
-
Yeah... guess what.
+* **\**
+
Yeah... guess what that might be.
 
 **Example**

WikiPage Menu reference modified by Thomas Luebking

Thomas Luebking — Mon, 02 Jul 2012 22:53:03 -0000

--- v2
+++ v3
@@ -2,7 +2,7 @@
 
 The global menu supports a customizable menu, found in ~/.kde/share/apps/be.shell/MainMenu.xml.
 The structure is:
-
+
     
         
             []
@@ -10,7 +10,7 @@
             []
         
     
-
+
 It's nearly the same code as in XBar (which was ported from BE::Shell)
 
 The first node is always ""
@@ -50,8 +50,8 @@
 
Yeah... guess what.
 
 **Example**
-
-
+
+    
     
     
         
@@ -61,5 +61,4 @@
         
     
     
-
-
+

WikiPage Menu reference modified by Thomas Luebking

Thomas Luebking — Mon, 02 Jul 2012 22:52:09 -0000

--- v1
+++ v2
@@ -2,6 +2,7 @@
 
 The global menu supports a customizable menu, found in ~/.kde/share/apps/be.shell/MainMenu.xml.
 The structure is:
+
     
         
             []
@@ -9,7 +10,7 @@
             []
         
     
-
+
 It's nearly the same code as in XBar (which was ported from BE::Shell)
 
 The first node is always ""
@@ -49,6 +50,7 @@
 
Yeah... guess what.
 
 **Example**
+
 
     
     
@@ -60,3 +62,4 @@
     
     
 
+

WikiPage Menu reference modified by Thomas Luebking

Thomas Luebking — Mon, 02 Jul 2012 22:45:48 -0000

# Custom menu # The global menu supports a customizable menu, found in ~/.kde/share/apps/be.shell/MainMenu.xml. The structure is: [] [] [] It's nearly the same code as in XBar (which was ported from BE::Shell) The first node is always "" To add a menu entry, add a "" node, this will add a popup menu. It's attributes can be either * **menu**
A reference to another xml file, following this very same structure (i.e. "inherit" another file) The path is relative to ~/.kde/share/apps/be.shell/ and an ".xml" suffix is applied automatically, eg. "subpath/submenu" turns to "~/.kde/share/apps/be.shell/subpath/submenu.xml" * **label** A label for the popup entry, defined in the following subnodes * **windowlist** Adds a window list, generated by BE::Shell * **BE::Config** Adds the BE::Shell config menu (the one you get by rightclicking on the Desktop) The actual popup menu entries can be subnodes * **
Yet another submenu * **
An active item, that actually triggers sth., can also be put directly into the node, though this is rather uncommon. It's attributes can be either * **label**
A label for the entry, overriding that in any given service * **icon**
An icon for the entry, overriding that in any given service * **dbus**
A dbus call, separate by semicolons. ;;;;[;[;[;...]]] * **exec**
either a service name or an executable, or a path, or ... basically anything you can type into krunner or konqueror, ie. "gg:KDE" will google for KDE! If this is a service, it's label and icon can be overridden by the related attributes * ****
Yeah... guess what. **Example**