On Friday, December 31, 2010, Chani wrote: > assuming for the moment that the only option is to use QDBusServiceWatcher > to listen for all new dbus services and check if they're nepomuk. does > anyone know of a better way?
m_nepomukWatcher = new QDBusServiceWatcher("org.kde.NepomukServer",
QDBusConnection::sessionBus(), QDBusServiceWatcher::WatchForOwnerChange,
this);
that should get you a watcher that only triggers when org.kde.NepomukServer
comes or goes. efficient (the filtering is done on the dbus server side) and
easy :)
> for the second part... I was thinking KActivityIcon could either have a new
> availabilityChanged signal (but not in 4.6) or just emit infoChanged() as
> if the icon had changed.
the latter sounds good to me; the user of KActivityIcon probably doesn't care
particularly why the icon has changed, right?
> so.. what *I* think is the best solution: have KActivityInfo watch for the
> nepomuk dbus service, and emit infoChanged when it appears.
sounds good.
> -would it be better to have kactivitymanagerd emit an availabliityChanged
> signal in 4.7?
if there are no use cases for it, then imho no.
> -should KActivityInfo also emit an availabilityChanged signal in 4.7?
imho, no.
> -should KActivityConsumer watch for nepomuk too, and emit
> serviceStatusChanged?
imho, no.
--
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43
KDE core developer sponsored by Qt Development Frameworks
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
