Bug#361418: [Proposal] new Debian menu structure
On Tue, Apr 11, 2006 at 12:22:53AM +0200, Eduard Bloch wrote:
> #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.
Please take into account that Debian menu will only display modules
suitable for the running window-manager (because they use a specific
'needs' field that only this wm 'support'). So in effect you are just
renaming "WindowManagers/Modules" to "Window Managers/$wm Modules".
I am not a typical user, but I have 45 window-managers installed
so I have a hard time finding the single Modules subsection and
naming it "Foo WM Modules" will not make things any easier. That
might not make me the best judge of the issue, though.
Imagine a large red swirl here.