|
@ -27,9 +27,17 @@ by |
|
|
The menu entries that are generated by **xdgmenumaker** are localised |
|
|
The menu entries that are generated by **xdgmenumaker** are localised |
|
|
according to the running user locale settings. |
|
|
according to the running user locale settings. |
|
|
|
|
|
|
|
|
**xdgmenumaker** currently supports generating menus for //blackbox//, |
|
|
**xdgmenumaker** currently supports generating menus for: |
|
|
//compizboxmenu//, //fluxbox//, //fvwm//, //icewm//, //jwm//, //pekwm// |
|
|
- blackbox |
|
|
and //windowmaker//. |
|
|
- compizboxmenu |
|
|
|
|
|
- fluxbox |
|
|
|
|
|
- fvwm |
|
|
|
|
|
- icewm |
|
|
|
|
|
- jwm |
|
|
|
|
|
- pekwm |
|
|
|
|
|
- twm and compatible derivatives such as ctwm and vtwm |
|
|
|
|
|
- windowmaker |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
**xdgmenumaker** requires //Python 2.7// or //3.x//, //pygtk// |
|
|
**xdgmenumaker** requires //Python 2.7// or //3.x//, //pygtk// |
|
|
(for Python 2.7) or //pygobject// and //gobject-instrospection// |
|
|
(for Python 2.7) or //pygobject// and //gobject-instrospection// |
|
@ -311,6 +319,37 @@ xdgmenumaker command and restart pekwm all over again to update it. The |
|
|
advantage is that there will be no delay in displaying the menu. |
|
|
advantage is that there will be no delay in displaying the menu. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
: **TWM and Derivatives** |
|
|
|
|
|
|
|
|
|
|
|
You can create a menu for TWM running **xdgmenumaker** like this: |
|
|
|
|
|
|
|
|
|
|
|
``$ xdgmenumaker -f twm > ~/.twm-xdgmenu`` |
|
|
|
|
|
|
|
|
|
|
|
If you're using the standard TWM, then unfortunately you'll have to |
|
|
|
|
|
manually copy/paste the contents of the generated //~/.twm-xdgmenu// file |
|
|
|
|
|
into your //~/.twmrc// manually. You could then add something like this |
|
|
|
|
|
to your main menu definition: |
|
|
|
|
|
|
|
|
|
|
|
``` |
|
|
|
|
|
"Applications" f.menu "xdgmenu" |
|
|
|
|
|
``` |
|
|
|
|
|
|
|
|
|
|
|
It could be possible to create a script that updates the menus inside |
|
|
|
|
|
the main //~/.twmrc// settings file, but I'll leave that as an exercise |
|
|
|
|
|
for the user. |
|
|
|
|
|
|
|
|
|
|
|
If you're using CTWM or VTWM, instead of manually copy/pasting the menu |
|
|
|
|
|
contents into your settings file, you could just add an include line |
|
|
|
|
|
like this: |
|
|
|
|
|
|
|
|
|
|
|
``` |
|
|
|
|
|
sinclude(`/home/george/.twm-xdgmenu') |
|
|
|
|
|
``` |
|
|
|
|
|
|
|
|
|
|
|
//Note:// In order for this to work with VTWM, **vtwm** has to be called |
|
|
|
|
|
with the //-m// switch. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
: **WindowMaker** |
|
|
: **WindowMaker** |
|
|
|
|
|
|
|
|
There are two ways to have an XDG menu in WindowMaker. The first one, |
|
|
There are two ways to have an XDG menu in WindowMaker. The first one, |
|
|