[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 103215] kicker removes application link during application
From:       Michael Nottebrock <lofi () freebsd ! org>
Date:       2005-04-04 23:42:31
Message-ID: 20050404234231.29510.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=103215         




------- Additional Comments From lofi freebsd org  2005-04-05 01:42 -------
FWIW, I don't really see the problem with kicker managing its own set of .desktop \
files (copied from the original ones). On the contrary, it would be possible to do \
everything it does now and do neat extras at the same time.

It could easily handle moving stuff around from kicker->desktop->menu and vice versa, \
but it could also color-indicate stale links, do user-triggered cleanups of stale \
links (or automatic ones, per option), could notifiy the user of changes between the \
cached (and customized) .desktop files and the shipped ones. And it could easily \
implement all sorts of different behaviours for links in different locations or of \
different types, too. Just by adding one (or a half, since the cached .desktop files \
wouldn't really need to reference other .desktop files) extra level of indirection.


[prev in list] [next in list] [prev in thread] [next in thread]