On Fri, 2003-05-30 at 03:59, Morten Brix Pedersen wrote:
> I'm working on implementing the desktop menu specification for the menu
> package
> (the C++ version, not the "new" debmenu). I hope to have the first version
> available within the next month.
Awesome!
> 1) The sections that are normally used within the Category field in a .desktop
> file isn't the same as with menu. Here I have decided to make menu
> automatically convert a category into menus system. E.g. Category:
> Application;WordProcessor will be changed to Apps/Editors.
Right, we'll need a mapping to transition. But honestly, I think we
should take this opportunity to revamp our menu categories too.
> 2) The current menu files use a "needs" field to designate whether the
> application uses console or X11 (e.g. needs="text"). In our .desktop
> files, this field will be named X-Menu-Needs and will only be required
> for non-X11 applications. (so current GNOME/KDE .desktop entries won't
> have to be changed)
Makes sense to me.
> 3) The current menu files has a "package" field to designate which
> package must be installed before the menu file will be used. In our
> .desktop files, this field will be named X-Menu-Package. But I'm unsure
> whether we should still require this field. Not requiring it might break
> some menu entries; but requiring it will force us to change upstreams
> .desktop files with the addition of X-Menu-Package.
Probably what we should do to transition this is to get a list of all
the files in /{,usr/}{,s}bin/, and put that in the TryExec field. What
do you think?
