#include <hallo.h>
* Bill Allombert [Mon, Apr 10 2006, 11:57:48PM]:
> I would like to stress that modules menu entries use window-managers
> specific 'needs' fields and as such are not bound by the Debian menu
> sub-policy (each window manager can choose its own section for modules)
> so it is meant only as a best practice and a convenience (because it
> will be translated as part of the menu section translation).
>
> However it might be that 'Modules' alone is too vague. Any specific
> improvement welcome.
What about this one: as you pointed out the Modules submenu is not
heavily used. What about just putting the module entries of each WM
using them into separate ...-Modules submenus in the same hierarchy
level as the WM entries? Imagine:
-> IceWM
-> Window Maker
-> Foo WM
-> Foo WM Modules
\- Foo Background Setup
|- Foo Gadget Setup
|- Foo Other Module
-> Other WM
-> TWM
I think that would be a good compromise. The Module submenu's location
follows directly the Foo WM starting entry and is easy to find. And
if only few WMs are adding modules there, it would not significantly
increase the number of top menu entries. And who does really install
more than a handful of WMs using "Modules" entries? Having some
addigional *-Modules entries in the menu would not really hurt.
Eduard.
--
<McBulba> un nu?
<lx_jakal> hunger!
<retfie> durst!
<lx_jakal> ja, das auch
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
