|
@ -86,38 +86,39 @@ any other case. |
|
|
To generate an application menu for Fluxbox, you can run |
|
|
To generate an application menu for Fluxbox, you can run |
|
|
**xdgmenumaker** like this: |
|
|
**xdgmenumaker** like this: |
|
|
|
|
|
|
|
|
**$ xdgmenumaker -f fluxbox > ~/.fluxbox/xdg_menu** |
|
|
``$ xdgmenumaker -f fluxbox > ~/.fluxbox/xdg_menu`` |
|
|
|
|
|
|
|
|
and then change your main Fluxbox menu to include this file as a |
|
|
and then change your main Fluxbox menu to include this file as a |
|
|
submenu. For example, add this somewhere in your //~/.fluxbox/menu// file: |
|
|
submenu. For example, add this somewhere in your //~/.fluxbox/menu// file: |
|
|
|
|
|
|
|
|
**[include] (~/.fluxbox/xdg_menu)** |
|
|
``[include] (~/.fluxbox/xdg_menu)`` |
|
|
|
|
|
|
|
|
You can add the **xdgmenumaker** command as another item in your menu, |
|
|
You can add the **xdgmenumaker** command as another item in your menu, |
|
|
if you want to update it, without having to run the command manually |
|
|
if you want to update it, without having to run the command manually |
|
|
again: |
|
|
again: |
|
|
|
|
|
|
|
|
**[exec] (Update Fluxbox Menu) (xdgmenumaker -f fluxbox > ~/.fluxbox/xdg_menu)** |
|
|
``[exec] (Update Fluxbox Menu) (xdgmenumaker -f fluxbox > ~/.fluxbox/xdg_menu)`` |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
: **IceWM** |
|
|
: **IceWM** |
|
|
|
|
|
|
|
|
To generate an application menu for IceWM, run **xdgmenumaker** like this: |
|
|
To generate an application menu for IceWM, run **xdgmenumaker** like this: |
|
|
|
|
|
|
|
|
**$ xdgmenumaker -f icewm > ~/.icewm/appmenu** |
|
|
``$ xdgmenumaker -f icewm > ~/.icewm/appmenu`` |
|
|
|
|
|
|
|
|
or if you want icons in your menu: |
|
|
or if you want icons in your menu: |
|
|
|
|
|
|
|
|
**$ xdgmenumaker -i -f icewm > ~/.icewm/appmenu** |
|
|
``$ xdgmenumaker -i -f icewm > ~/.icewm/appmenu`` |
|
|
|
|
|
|
|
|
and you can then edit your //~/.icewm/menu// file and add this line |
|
|
and you can then edit your //~/.icewm/menu// file and add this line |
|
|
somewhere: |
|
|
somewhere: |
|
|
|
|
|
|
|
|
**include appmenu** |
|
|
``include appmenu`` |
|
|
|
|
|
|
|
|
You can add the **xdgmenumaker** command as another item in your menu, if |
|
|
You can add the **xdgmenumaker** command as another item in your menu, if |
|
|
you want to update it, without having to run the command manually again: |
|
|
you want to update it, without having to run the command manually again: |
|
|
|
|
|
|
|
|
**prog "Update Menu" _none_ xdgmenumaker -i -f icewm > ~/.icewm/appmenu** |
|
|
``prog "Update Menu" _none_ xdgmenumaker -i -f icewm > ~/.icewm/appmenu`` |
|
|
|
|
|
|
|
|
//NOTE:// If you don't request icons in the menu, or if an icon is not found |
|
|
//NOTE:// If you don't request icons in the menu, or if an icon is not found |
|
|
for a certain app, the icon name in the menu for that app is set to |
|
|
for a certain app, the icon name in the menu for that app is set to |
|
@ -126,6 +127,7 @@ IceWM menu entries should always include an icon . So, by pointing it |
|
|
to a non existing icon, you essentially set it to use no icon. If you |
|
|
to a non existing icon, you essentially set it to use no icon. If you |
|
|
actually have an icewm icon named "_none_", that one will be used instead. |
|
|
actually have an icewm icon named "_none_", that one will be used instead. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
: **pekwm** |
|
|
: **pekwm** |
|
|
|
|
|
|
|
|
There are two ways to have an XDG menu in pekwm. The first one, |
|
|
There are two ways to have an XDG menu in pekwm. The first one, |
|
@ -145,26 +147,27 @@ Entry = "" { Actions = "Dynamic /usr/bin/xdgmenumaker -n -i -f pekwm --pekwm-dyn |
|
|
Restart pekwm and the generated menu should appear. The menu will be |
|
|
Restart pekwm and the generated menu should appear. The menu will be |
|
|
automatically generated every time you access it, so it will always be |
|
|
automatically generated every time you access it, so it will always be |
|
|
up to date. But since xdgmenumaker will run every time you access the |
|
|
up to date. But since xdgmenumaker will run every time you access the |
|
|
menu, the menu might not appear instantly. |
|
|
menu, the menu might not appear instantly, especially if you are using |
|
|
|
|
|
an older PC. |
|
|
|
|
|
|
|
|
**Static Menus** |
|
|
**Static Menus** |
|
|
|
|
|
|
|
|
Run |
|
|
Run: |
|
|
``` |
|
|
|
|
|
$ xdgmenumaker -n -i -f pekwm > ~/.pekwm/appsmenu |
|
|
``$ xdgmenumaker -n -i -f pekwm > ~/.pekwm/appsmenu`` |
|
|
``` |
|
|
|
|
|
to create a file with the menu contents. Then edit your |
|
|
to create a file with the menu contents. Then edit your |
|
|
//~/.pekwm/menu// file to include that menu, by adding a line like the |
|
|
//~/.pekwm/menu// file to include that menu, by adding a line like the |
|
|
following, in the location that you want the menu to appear: |
|
|
following, in the location that you want the menu to appear: |
|
|
``` |
|
|
|
|
|
INCLUDE = "/home/your_user_name/.pekwm/appsmenu" |
|
|
``INCLUDE = "/home/your_user_name/.pekwm/appsmenu"`` |
|
|
``` |
|
|
|
|
|
|
|
|
|
|
|
Restart pekwm and the generated menu should appear. The menu is static |
|
|
Restart pekwm and the generated menu should appear. The menu is static |
|
|
and if you add/remove any applications, you will have to run the |
|
|
and if you add/remove any applications, you will have to run the |
|
|
xdgmenumaker command and restart pekwm all over again to update it. The |
|
|
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. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
: **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, |
|
@ -175,14 +178,14 @@ updates the menu only when the user wants to. |
|
|
and has been tested only with wmaker-crm>=0.95.1. No idea if utf8 works |
|
|
and has been tested only with wmaker-crm>=0.95.1. No idea if utf8 works |
|
|
properly with older WindowMaker versions. |
|
|
properly with older WindowMaker versions. |
|
|
|
|
|
|
|
|
**Method 1** |
|
|
**Dynamic Menus** |
|
|
|
|
|
|
|
|
Open the WindowMaker preferences tool. In the //Application Menu |
|
|
Open the WindowMaker preferences tool. In the //Application Menu |
|
|
Definition// section, add a //Generated Submenu// in your menu, by dragging it |
|
|
Definition// section, add a //Generated Submenu// in your menu, by dragging it |
|
|
in. Click on the menu item you just dragged in and in the preferences |
|
|
in. Click on the menu item you just dragged in and in the preferences |
|
|
window, in //Command//, add: |
|
|
window, in //Command//, add: |
|
|
|
|
|
|
|
|
**xdgmenumaker -f windowmaker** |
|
|
``xdgmenumaker -f windowmaker`` |
|
|
|
|
|
|
|
|
Save and close the preferences window. |
|
|
Save and close the preferences window. |
|
|
|
|
|
|
|
@ -192,11 +195,11 @@ that with running this command every time, especially if |
|
|
you are on a very old PC, it might slow things down a bit. Even then it |
|
|
you are on a very old PC, it might slow things down a bit. Even then it |
|
|
is probably not anything considerable. |
|
|
is probably not anything considerable. |
|
|
|
|
|
|
|
|
**Method 2** |
|
|
**Static Menus** |
|
|
|
|
|
|
|
|
Run |
|
|
Run: |
|
|
|
|
|
|
|
|
**$ xdgmenumaker -f windowmaker > ~/GNUstep/Defaults/xdg_menu** |
|
|
``$ xdgmenumaker -f windowmaker > ~/GNUstep/Defaults/xdg_menu`` |
|
|
|
|
|
|
|
|
Then open the WindowMaker preferences tool and in the //Application Menu |
|
|
Then open the WindowMaker preferences tool and in the //Application Menu |
|
|
Definition// section, add an //External Submenu// by dragging it in your menu. |
|
|
Definition// section, add an //External Submenu// by dragging it in your menu. |
|
@ -204,7 +207,7 @@ Click on the menu item you just dragged in and in the preferences |
|
|
window, in //Path for Menu//, add the location of the menu file you just |
|
|
window, in //Path for Menu//, add the location of the menu file you just |
|
|
created: |
|
|
created: |
|
|
|
|
|
|
|
|
**~/GNUstep/Defaults/xdg_menu** |
|
|
``~/GNUstep/Defaults/xdg_menu`` |
|
|
|
|
|
|
|
|
You can add the above mentioned **xdgmenumaker** command as another |
|
|
You can add the above mentioned **xdgmenumaker** command as another |
|
|
item in your menu, if you want to update it, without having to run the |
|
|
item in your menu, if you want to update it, without having to run the |
|
@ -217,7 +220,7 @@ mentioned above. |
|
|
|
|
|
|
|
|
The downside of this method, is that the menu contents will not be |
|
|
The downside of this method, is that the menu contents will not be |
|
|
updated when you install a new application or remove one. You will need |
|
|
updated when you install a new application or remove one. You will need |
|
|
to run the xfgmenumaker command every time you want the menu to be |
|
|
to run the xdgmenumaker command every time you want the menu to be |
|
|
updated. The upside is that the menu will not be generated every time |
|
|
updated. The upside is that the menu will not be generated every time |
|
|
you access the menu. This might be a better choice for (really) older |
|
|
you access the menu. This might be a better choice for (really) older |
|
|
hardware. |
|
|
hardware. |
|
|