Menu-Spec and nested AppDirs

[Heinrich Wendel]

On Thursday 26 May 2005 18:05, Mark McLoughlin wrote:
>   2) That you give edited files a different desktop file ID so that you
>      no longer have to worry about the order of <AppDir>s in the .menu
>      file when you're implementing a menu editor which
>      modifies .desktop files.
>
>      I think this makes sense for various reasons, but to give one
>      example - consider a .desktop file which is <Include>d in two
>      menus. If a user edits an entry in one menu, she wouldn't also
>      expect it to change in the other menu. (Yes, its a corner case
>      but ....)
>
>      Anyway, its this ".desktop file renaming" part of my suggestion
>      which is really more relevant to the problem you're pointing out.

What about this:

We only have a global pool of AppDirs/DirectoryDirs, not a local one for every 
menu. AppDirs/DirectoryDirs in Submenus are added at the end of that global 
pool, so they have priority. To prevent collisions the AppDirs/DirectoryDirs 
might have a prefix attribute. Additionally AppDirs/DirectoryDirs that are in 
the Users's folder always have priority instead of the System wide dirs.

> Cheers,
> Mark.
mfg, heinrich :-)