On October 6, 2009, PierreL wrote: > The thing is now, with this plasmoid already added in a previous KDE > session, when KDE starts, it seems, plasma is started before Nepomuk > service or maybe I'm wrong, but the plasmoid's model is empty (not > populated with any Nepomuk data).
either individual plasmoids need to track the availability of services, or we need to provide a way in libplasma to do this. right now we have the following important services that can modify the behaviour of Plasmoids: * compositing (status available via Theme; Svg's are updated) * power (Applet::shouldConserverResources; but no status change notification) * network (each plasmoid must do it via Solid::Networking, which provides both current info as well as change notification) * nepomuk (each plasmoid must do it by checking dbus connections) if this collection continues to grow, it might be a good idea to have some mechanism generally available to track them. one way to do this without adding API to libplasma would be to write a DataEngine that starts tracking a given resource when a source is requested by that name. e.g. if the "nepomuk" source is requested, it would create a nepomuk source with perhaps { "available" => bool } as the data and update the source whenever the resources becomes available or not. -- 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