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

Re: [menus] pending issues



Yeah, I'm thinking more of XML elements rather than the .desktop files
themselves, ie the .desktop file dies but the elements referring to it
for moving/hiding the entry remain, leading to registry-style cruft
buildup.

On Mon, 2002-12-16 at 19:04, Nils Pedersen wrote:
> Mike Hearn wrote:
> 
> <snip>
> 
> >
> >What about entries that are deleted/moved, then their .desktop file disappears
> >(ie it's uninstalled). Is there any specified system for eliminating "dead"
> >entries in this way? Otherwise menu definition cruft would accumulate. Oh - this one
> >also bit me in a way I wasn't expecting: I installed our foobar test app, the menu
> >entry appeared, deleted it from the menu then uninstalled the app. OK. Reinstall the
> >app, and of course the menu entry doesn't appear. Although it could be argued it's
> >better to persist move/delete changes between installations, users conventional wisdom
> >says that when you install an app a menu entry appears regardless of what might have
> >been done before - if anything, "reinstall the app" is a common tech support answer so
> >it'd be bad to have things magically remembered between sessions in that way.
> >
> Well the policy that Solaris has adopted is that the .desktop is 
> delivered with the application package. So when the
> application/package is removed so is the .desktop. IIRC, for GNOME 2.0 a 
> lot of .desktops were moved from a
> central module to their respective application's module.
> 
> Nils
-- 
Mike Hearn <mike theoretic com>





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