On Tuesday 28 March 2006 00:27, foser wrote:
> I'm aware of the issues surrounding menus, but the spec gives a lot of
> options. As said, we haven't dealt with it, because it is not a snag
> that we hit currently.
>
> I think we can basically have several menu setups fit for different
> tasks/DEs and either let loginmanagers choose on startup or users choose
> on install.
>
> I don't know what the future plans are of KDE regarding it's slotting,
> but if it intends to use syswide (fdo) specs like mime/icons the install
> alternate root is going to be the main hurdle to tackle.
If we make a system for selecting menu items. etc on a per-session basis, like 
you describe above, then I think we can easily support arbitrary additional 
install locations, specified in env.d or session files.

I like the idea, now we need to actually design and build such a system :-)

Do you think all fdo items should be controlled by it and not just menu items? 
Or should some things always be available (at least by default)? I'm in favor 
of making everything else available by default (services and so on) because 
1) I think it's easier using fdo specs - menu files already support filtering 
and 2) the main complaint against having everything in the menus is clutter, 
and that's not as big a problem with e.g. filemanager context menus.

-- 
Dan Armak
Gentoo Linux developer (KDE)
Public GPG key: http://dev.gentoo.org/~danarmak/danarmak-gpg-public.key
Fingerprint: DD70 DBF9 E3D4 6CB9 2FDD  0069 508D 9143 8D5F 8951