"Dan Espen" <des...@verizon.net> wrote:
>I see:
>File locations
>Files involved in this specification are located according to the
>"desktop base directory specification".
>
>Here are the files defined by this specification:
>$XDG_CONFIG_DIRS/menus/${XDG_MENU_PREFIX}applications.menu
>
>But on my Fedora system, I have
>/etc/xdg/menus/applications-gnome.menu
>
>Which is part of the gnome-menus-3.2.0.1-1.fc16.i686
>package. Looks like it doesn't care about that rule.
>
>Then there are all the other menus in the xdg/menus area.
>They don't end in "applications" either.
These are optional menus. The main menu is applications.menu
>I mean, I see it in the xdg spec and I see what you'd like to do with
>accessing "applications". But I don't see how this fits with the
>other xdg menus we might want to access which don't have rules like this.
fvwm-menu-desktop is absolutely xdg compliant
--desktop fits ${XDG_MENU_PREFIX} like gnome-, kde4-, xfce-, lxde-
--menu-type specifies the type like applications, preferences, settings
and for non compliant menus all other named stuff ...
And we can map *ALL* menus - compliant and non compliant ones:
applications-gnome.menu
--menu-type=applications-gnome
applications.menu
*standard* (no parameter needs to set)
documentation.menu
--menu-type=documentation
gnomecc.menu
--menu-type=gnomecc
kde4-applications.menu
--desktop=kde4(-)
kde-information.menu
--desktop=kde(-) --menu-type=information
preferences.menu
--menu-type=preferences
server-settings.menu
--desktop=server(-) --menu-type=settings OR
--menu-type=server-settings
settings.menu
--menu-type=settings --title=FvwmSettings
start-here.menu
--desktop=start(-) --menu-type=here OR
--menu-type=start-here
system-settings.menu
--desktop=system(-) --menu-type=settings
applications-gnome.menu
--desktop=applications(-) --menu-type=gnome
kde4-applications.menu
--desktop=kde4(-)
Okay, it's not nice how the parameters are misused but menus like
applications-gnome.menu are poor also. And they doesn't follow the xdg spec.
>Not happy with the whole scheme.
>Convince me not to dump it.
What we can do is to rename the parameters like
--desktop -> --menu-prefix
--menu-type -> --menu-postfix
>Seems to me, the best way fvwm can interface with this mess
>is to just treat the whole name as one thing.
To merge --desktop and --menu-type to e.g --menu-name would anul the
xdg automatism.
All systems that I've analyzed has an applications.menu (except Debian)
and they use mostly a {gnome,kde4,kde,xfce,lxde,...}-applications.menu
for each installed desktop environment. Also for system wide menus like
preferences, settings: no ${XDG_MENU_PREFIX} infront and if there is a desktop
specific one they added the desktop name (kde4-settings). From that
point of view
all is ok with the implementation in fvwm-menu-desktop (except that we not check
the Env var ${XDG_MENU_PREFIX} as is described in the xdg spec).
The only thing what I would do is, if you prefer the complete prefix as an
argument renaming --desktop to --menu-prefix because --desktop associates
to use a desktop name *without* a trailing '-'
Thomas
Btw about renaming ... we should rename the following parameters for better
understanding:
--size -> --icon-size or --mini-icon-size
--with-titles -> --with-menu-titles
With the last one I am in doubt. It's every time a tightrope walk between
short as possible and a maximum of expressiveness.
