[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kfm-devel
Subject:    Re: Fwd: Bug#992: menus and applnk directory
From:       Sven Radej <sven () lisa ! exp ! univie ! ac ! at>
Date:       1999-03-18 8:54:34
[Download RAW message or body]

>----- Forwarded message from Alexander A Kirillov <kirillov@IAS.EDU> -----
>
>Subject: Bug#992: menus and applnk directory
>Date: 	Wed, 17 Mar 1999 15:17:38 -0500 (EST)
>From: Alexander A Kirillov <kirillov@IAS.EDU>
>To: submit@bugs.kde.org
>
>package: kfm
>severity: wishlist
>
>Hi,
>I would much appreciate if we could have a little more control over
>which .kdelnk files are scanned by KFM and what is placed in menus. As
>far as i understand, at the moment KFM scans both personal and system
>applnk directories (and tries to hide this from the user pretending
>that all of these files live in personal applnk directory); and kpanel
>also scans these directories and places them in the root menu. What
>I'd like is: 
>
>1. to make it possible to have applications which are scanned by KFM
>but not placed in the menu
Maybe to put something like "notInMenu" entry in kdelnk?

>2. to make it possible to exclude some (or all) of the system default
>applications from being scanned or included in the menu.
That would require for user to create same kdelnk in personal folder and make
it have "notInMenu" entry.
If root wants some bindings which he globaly wants to prevent from showinf up
in menus, then he should put "notInMenu" entry in them.
And if root wants to prevent users from overriding some global bindings, he
should add something like "noOverride" entry there.

There should be not many such items so this method would - IMHO - make smaller
slowdown than scanning another subdir.
--
Sven Radej     radej@kde.org
KDE developer   Visit http://www.kde.org

[prev in list] [next in list] [prev in thread] [next in thread]