KDED Modules and their DBus Path

Ralf Habacker ralf.habacker at freenet.de
Mon Apr 21 21:19:17 BST 2008


Michael Jansen schrieb:
> Hi 
>
> I have a comment on the kded modules and a problem i see. Probably it's only 
> in my imagination so i put it up here for comments.
>
> I'm no dbus expert so forgive the most probably wrong wording :-) .
>
> Currently those modules put up their interface under 
> org.kde.kded/modules/<modulename> . I think that's not optimal. 
>
> Beeing a kded module is an implementation detail that is exposed to the world 
> by that usage. Whenever we have to change a module back to a standalone daemon 
> we have a problem. Shouldn't kded modules register their Interface under 
> org.kde.<module> if they provide an non trivial api for scripters?
>
> I don't think it's worth to change any code for that, i just wanted to get 
> some opinions.
>   
May be this could be archived by adding an additional KDEDModule 
constructor parameter which adds an additional or switch to a module 
registration name outside of the kded namespace.

Ralf





More information about the kde-core-devel mailing list