[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Debian packages and freedesktop.org (Gnome, KDE, etc) menu entries



Cameron Patrick wrote:

> On Fri, Dec 12, 2003 at 04:12:58AM +0100, Moritz Moeller-Herrmann wrote:

> | This is not true. Almost all features are being used in current KDE and
> | to some degree by current GNOME. Could you please give examples?
 
> The Categories= field (to place .desktop files into menu hierarchies) is
> AFAIK not used at all by KDE, although I think Gnome may support it.
> The freedesktop 'menu' standard (where sub-menus can be generated from
> the categories in the .desktop files, and which also claims to allow
> "legacy" menus to be merged with the new standard) doesn't seem to have
> been adopted yet by anyone. 

It is supported and used in KDE-3.2beta. KDE-3.2 should be released in
January.

> The worst part, though, is that currently 
> both KDE and Gnome store their .desktop files in different places, so
> that a .desktop that is available to KDE (and placed in /usr/lib/applnk)
> won't automatically appear in the Gnome menu, which looks in
> /usr/lib/applications.  I presume that these things are being worked on
> in later releases of KDE and Gnome, but I don't know where to look for
> the current status of their adoption of the freedesktop.org standards.

Again, please have a look at KDE-3.2. I am currently using the KDE CVS
debian snapshots. KDE stores all it's desktop files in /usr/share
applications and GNOME uses the same directory. 
Of course the system can and will be improved, once it is generally adopted.

> I have also noticed what might be considered as 'abuse' of these
> standards, presumably due to poor implementation of some fields.  For
> example, /usr/share/applications/epiphany.desktop lists its Name as "Web
> Browser"; it should more correctly list its name as "Epiphany" and have
> a GenericName field containing "Web Browser".

Not all desktop files are perfect yet. Especially those not part of the DE.
But this should not be fixed downstream.



Reply to: