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

List:       kde-core-devel
Subject:    Re: Some KMenu thoughts
From:       m_elter () t-online ! de (Matthias Elter)
Date:       2002-02-02 12:38:13
[Download RAW message or body]

Raffaele Sandrini wrote:

> From time to time i get emails saying that there is no way to change root 
> links in Kicker. This is true so far. 
>  
> So we have to thinks about this. It would be the best if any user (not only 
> root) can change the look of his desktop. Perhapps he also doesn't want all 
> those links in the KMenu because there are some wich he will never use. There 
> comes the problem. There is no way to get them out of the Menu because they 
> are stored in $KDEDIR/share/applnk wich is normally onyl accessable by root. 
> He can only change and remove those items wich he has created by himself. 
>  
> I think we should handle this. A possible solution would be that when the user 
> starts KDE first time the whole linktree would be copied to 
> $HOME/.kde/share/applnk and kicker would take his informations only from 
> there. The user would be free then to make everything. An other approach 
> would be create special files in the Home dir to tell kicker not to show a 
> specific link. E.g. for $KDEDIR/share/applnk/System/kwuftpd.desktop there 
> would be a $HOME/.kde/share/applnk/System/kwuftpd.hide or something like 
> that. 
>  
> Asking for pros and contras and general comments :-). 


What happened to the "masking" feature I added to kmenuedit in Trysil? 
IIRC removing global menu entries used to work by having a copy of the 
.desktop file in the users local menu structure with some kind of 
"removed" attribute.

Making a copy of the whole menu structure on first login is a bad idea 
because it makes global admin changes (adding applications etc.) 
impossible. Storing user changes only in the local menu structure is the 
way to go.

Greetings,
Matthias

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