XDG Desktop Menu Specification - issues

Waldo Bastian bastian at kde.org
Tue May 6 12:02:32 BST 2003

Hash: SHA1

On Tuesday 06 May 2003 05:26, Havoc Pennington wrote:
> > This would all be much easier if the AppDir entries all had global scope,
> > then you could safely use $XDG_DATA_HOME/applications to override any of
> > them.
> If I understand what you're saying:
>  - you have the kword.desktop menu item in two places and edit only one
>  - you would create a new kword.desktop in $XDG_DATA_HOME/applications
>  - that would globally override everything called kword.desktop
>  - both instances of KWord would change name
> I think users would expect that only one instance would change
> name. For example, they might be editing one kword item to be "new
> document with resume template" or something, so changing both Name=
> and Exec=. A reasonable way to do that might be to copy the kword
> item, then modify one of them. To make this work right you have to do
> the mkstemp()-style copy of the .desktop file right?

Editing a menu-item that appears in the menu twice creates a whole set of 
problems of it's own. I was just considering the case where there is a single 
"KWord" entry which the user edits to include e.g. "--extra-option" on the 
command line. You don't want to create a second .desktop file in that case. 
It should remain kword.desktop just with a different Exec=-line.

It's not clear at all to me how to handle the situation with duplicated 
entries. If there are two KWord entries in the menu then what is the 
intention of the user when he edits one and adds "--extra-option"? Should 
that only apply to that one entry, or also to the other? Which .desktop entry 
should be used when clicking on a KWord-file?

- -- 
bastian at kde.org -=|[ SuSE, The Linux Desktop Experts ]|=- bastian at suse.com
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org


More information about the kde-core-devel mailing list