XDG Menus Revisited
I’ve been messing around with a better way to use xdg-menus with openbox, my first attempt was both clumsy and not very generic (not everyone has their menus set up exactly like me…) I’ve reworked the whole ordeal into a simple script that will pull the pipemenu, swap your menu.xml and write the xdg-menu in the fist instance, there are even instructions on how to automate it to react to adding and removing software, using fsniper.
You can get the script here:
Because I now have an xdg-menu I’ve had to add a few custom .desktop files and make a couple of scripts to make the change easier.
They are all here:
http://github.com/mulberry/obtools/
The bluetooth script is the one that was most hassle as I have no idea what I am doing, but it basically uses zenity and bluez utilities to scan for bluetooth devices and then mount them with obexfs and show the dir in thunar, I guess the thunar bit is optional? There is an openbox pipemenu in there that does pretty much the same but it is really slow due to the scanning. You still need to bond the devices first but that’s your business how you do that 
.
There is also a simple zenity monstrosity to exit openbox if you are using it to manage your session.
That is all I got.
an xdg root menu sort of thing for openbox
Here are a mess of a scripts that give you a xdg root menu, based on the xdg-menu. It is not very dynamic as you have to refresh it on changes. There is probably a way to automate this on package installation/removal or by editing with alacarte or similar.
The crux of it is to generate a menu file (rootmenu.xml) that is then read as a pipe menu ( ‘cat rootmenu.xml’ -> this was Mikachu’s idea). This makes it as quick as a normal menu as it is not built on demand, sort of like a cached pipemenu, and then set to display as your root menu, rather than a normal pipe sub menu. A couple of other files are included to make managing the menus easy.
Very vague instructions are included.