Activities API

[Ivan Čukić]

> is for KActivities::Info ?
> I have to actually think more about it, but just at a glace i would leave
> the
> info api as it is now but not creatable, but to be asked with a kjob.
>

I'd rather then have a KJob* fetchProperties() than having a kjob create
the instance - especially since KJob's API doesn't tell anything about
returning the result of something (that is I why I liked
QFuture<Something>). Or, just a propertyFetched() signal.


> the thing i am less happy actually is the dbus api, i don't think every
> property of every api should be a separate method. on dbus it big


+1 Something I've started to deal with.

-- 
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/20130907/a2ae7361/attachment.html>