[kubuntu-users] KDE menus

[Derek Broughton]

On Friday 27 May 2005 12:19, Jonathan Riddell wrote:
> On Fri, May 27, 2005 at 11:38:27AM -0300, Derek Broughton wrote:
>
> > However, there are many KDE utilities that have no menu entries (e.g.,
> > kappfinder), and reinstalling still doesn't create one, even though it
> > apparently should.
>
> If you look in
>
> /usr/share/applications/kde/kappfinder.desktop
>
> You'll see I added
>
> Hidden=true
>
> which has been added to various .desktop files to keep the menu
> simple.

I've got nothing against keeping the menu simple, but there needs to be a 
reasonably simple way to get these desktop files _back_ into the menu if you 
want them.  The reason I was looking for kappfinder was specifically to see 
if it could help with this - and afaict, it can't.  It's silly that I can add 
X apps to the menu with kappfinder, but I can't add KDE apps!

> Actually it should be NoDisplay=true, that'll be fixed for breezy.
>
> > Then when I installed CrossOver office, I couldn't get the CrossOver menu
> > entries either.
>
> Where does it install it's .desktop files and what does the
> Categories= field say?

No categories - which I suspect is the problem, but there needs to be a way 
for legacy apps to get into the menu.  If I'm right about this, it would seem 
that the default /etc/xdg/menus/kde-applications.menu needs to have an entry 
somewhere with <INCLUDE><CATEGORY>Legacy</CATEGORY><INCLUDE>, right?

In both /etc/xdg/menus/applications-merged and 
~/.config/menus/applications-merged there is a cxlegacy.menu file, which 
contains:
<!DOCTYPE Menu PUBLIC "-//freedesktop//DTD Menu 1.0//EN" 
"http://www.freedesktop.org/standards/menu-spec/1.0/menu.dtd">
<!-- File Created by CrossOver Office cxmenu -->
<Menu>
  <Name>Applications</Name>
<LegacyDir>/home/derek/cxoffice/support/xdg-legacy-menus</LegacyDir></Menu>

which also looks right.  The xdg-legacy-menus directory contains two 
directories, which in turn contain other directories or .desktop files - 
which seems to be exactly what a <LegacyDir> should have.
-- 
derek