> hmm. am i reading this correctly that this kded service is only needed if > nepomuk is not there, and that it serves as a cache-in-the-middle between > nepomuk and the applications? this seems like a lot of overhead just to
this was one of the kwin people wishes. Even with nepomuk, a cache-in-the middle is benefitial here since we don't really need the overhead of querying nepomuk when a user switches the activity. > there there is the topic of signals ... dbus signals suck majorly. they are > broadcast to every application on the bus whether they care or not. might > it be better if ActivityConsumer registered itself over dbus with the kded > service which would then call async methods on these registered objects as > needed? this is what we're doing with jobs, notifications and the system > tray. Ok. We could do that - I had no idea dbus signals were that badly designed. > it has signals for document association; what about other resources? The same comment as in the previous mail. Cheerio, Ivan -- Those people who think they know everything are a great annoyance to those of us who do. -- Isaac Asimov _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
