The usage statistics [kactivities, baloo, ktp, plasma]

[Ivan Čukić]

> Kicker currently uses Muon, which is part of the workspace.
> We can [...]

Yes, I would go for that, unless we really see that it is needed to be
accessible by kactivities data models.

Ch


On 22 October 2014 15:07, Vishesh Handa <me at vhanda.in> wrote:

>
> On Tue, Oct 21, 2014 at 11:35 PM, Eike Hein <hein at kde.org> wrote:
>
>> As I recall, this was implemented inside Kickoff itself.
>> I *think* it maintained a timestamped lists of new apps
>> when discovering them as it build up the menu structure
>> on startup or so ...
>>
>> I'm guessing something similar would be an avenue to
>> getting it back - KAMD could diff ksycoca scans, or
>> react to ksycoca change signals, and slam newly-dis-
>> covered apps as CREATED into its db ...?
>>
>
> I'm a little confused about why we need this data to be stored in KAMD as
> a created event.
>
> 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.
>
> --
> Vishesh Handa
>
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel at kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>
>


-- 
Cheerio,
Ivan

--
While you were hanging yourself on someone else's words
Dying to believe in what you heard
I was staring straight into the shining sun
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20141022/d135bf2c/attachment-0001.html>