D-BUS interfaces and whatnot (Re: KDE/kdebase/konqueror/settings/performance)
Thiago Macieira
thiago at kde.org
Wed Jun 7 19:37:45 BST 2006
Richard Dale wrote:
>Yes, that looks good. It expects:
>dbus <service> <path> <interface> <member> arg(s)
No, it expects:
dbus <service> <path> <interface>.<member> arg(s)
or
dbus <service> <path> <member> arg(s)
>What naming conventions should it be using. Should the
> q_classinfo/Q_CLASSINFO specifiy 'org.kde.<appname>.MyWidget' ?
If the interface you're exporting is local to your application, yes,
please prefix your interface name with the application's name.
If it's a global KDE interface (i.e., something that we as KDE tell the
world they can use, including ourselves), then it should be in org.kde.
Normally, you keep lowercased the domain part, but you uppercase that
which is not part of the domain. So, for instance,
org.kde.kopete.InstantMessenger is ok because kopete.kde.org exists. For
applications without domain, we can safely pretend that the domain exists
in kde.org.
For applications that have their own domain, it's their choice. For
instance, amaroK could choose to use org.amarok instead of
org.kde.amarok. KOffice applications will use org.koffice.appname.
> Am I supposed to call registerObject() with a "/" or "/MyWidget"
> or "/<appname>/MyWidget" path? I can't seem to quite get a grip on it.
You choose.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
thiago.macieira (AT) trolltech.com Trolltech AS
GPG: 0x6EF45358 | Sandakerveien 116,
E067 918B B660 DBD1 105C | NO-0402
966C 33F5 F005 6EF4 5358 | Oslo, Norway
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20060607/10e568b1/attachment.sig>
More information about the kde-core-devel
mailing list