Openbox: Generating a Menu from your Self-Written Scripts

I have a collection of scripts for various tasks, which reside in ~/.bin/ Some of them start graphical programs like games installed with wine and similar stuff. I wanted an easy way to add these scripts to my Openbox menu. Thanks to openbox' pipe-menu functionality this is quite easy to do.

The Menu Script

First lets take a look at the script that generates the menu. It is called and lies alongside my other scripts in ~/.bin:



for i in ${_SCRIPTDIR}/*.msh
        echo -n "$(grep "MCATEGORY" < ${i} | cut -d'=' -f2);" >> /tmp/scriptmenu.$$
        echo -n "$(grep "MNAME" < ${i} | cut -d'=' -f2);" >> /tmp/scriptmenu.$$
        echo "${i}" >> /tmp/scriptmenu.$$

sort > /tmp/scriptmenu_s.$$ < /tmp/scriptmenu.$$

cut -d';' -f1 < /tmp/scriptmenu_s.$$ | uniq > /tmp/menucat.$$

echo '<?xml version="1.0" encoding="utf-8"?>'
echo '<openbox_pipe_menu>'
while read line
        echo "  <menu id=\"sm-${line}\" label=\"${line}\">"
        while read -a line2
                if [ "${line}" == "${line2[0]}" ]
                        echo "  <item label=\"${line2[1]}\">"
                        echo "    <action name=\"Execute\">"
                        echo "      <execute>"
                        echo "        ${line2[2]}"
                        echo "      </execute>"
                        echo "    </action>"
                        echo "  </item>"
        done < /tmp/scriptmenu_s.$$
        echo "  </menu>"
done < /tmp/menucat.$$
echo '</openbox_pipe_menu>'

rm /tmp/*.$$

Preparing the Scripts for the Menu

Since I don't want all of the scripts in the menu (many of them are terminal-progs without an UI) I thougt about a way to select the wanted scripts. Since my scripts are normally called <something>.sh I name all scripts that shall apear in the menu <something>.msh (for menu-script). A second thing I wanted to have is a posibility to define names and categories for the scripts independent from their filename. So I use 2 “variables” inside the script for defining these. Have a look at my Guild Wars starter script for example:

#MNAME=Guild Wars

export WINEPREFIX="/mnt/data/Games/Guildwars"
export WINEDEBUG="-all"
wine C:\\Programme\\GuildWars\\Gw.exe

The important part here are the lines 2 and 3. MCATEGORY defines the Category to use, and MNAME obviously the name for the menu entry. These two lines have to be present in every script or the menu-generation will fail. Everyhing before MCATEGORY/MNAME is ignored (so they can be comments like in the example above), and everything after the “=” will be used as category label or name.

Including it into the Openbox Menu

The last part is encluding the menu-script in the openbox menu as a pipemenu. This is as easy as adding the following line to ~/.config/openbox/menu.xml at the position you want the menu to appear:

<menu execute="/home/seiichiro/.bin/" id="scriptmenu" label="Scriptmenu"/>


Thats it, here is a screenshot of the script in action. everything below “Scriptmenu” is generated on the fly:



Like all my other scripts I present here, I give absolutely no guaranty for the function or correctness of the script. I also can't be held responsible if anything bad happens from using it like destruction of data or similar. Feel free to adapt it to your needs and don't hesitate to use the comments area below for questions or suggestions.


blog/openbox_generating_a_menu_from_your_self-written_scripts.txt · Last modified: 28.09.2010 13:36 by Seiichiro
CC Attribution-Share Alike 3.0 Unported
Driven by DokuWiki Hosted by Linode Recent changes RSS feed Valid XHTML 1.0