<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 21, 2014 at 11:35 PM, Eike Hein <span dir="ltr"><<a href="mailto:hein@kde.org" target="_blank">hein@kde.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":213" class="a3s" style="overflow:hidden">As I recall, this was implemented inside Kickoff itself.<br>
I *think* it maintained a timestamped lists of new apps<br>
when discovering them as it build up the menu structure<br>
on startup or so ...<br>
<br>
I'm guessing something similar would be an avenue to<br>
getting it back - KAMD could diff ksycoca scans, or<br>
react to ksycoca change signals, and slam newly-dis-<br>
covered apps as CREATED into its db ...?</div></blockquote></div><br>I'm a little confused about why we need this data to be stored in KAMD as a created event.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Kicker currently uses Muon, which is part of the workspace. We can quite easily just ask it for newer applications and avoid having to diff ksyscoca scans and react to any signals or anything.</div><div class="gmail_extra"><div><br></div>-- <br><span style="color:rgb(192,192,192)">Vishesh Handa</span><br>
</div></div>