KDE4's IPC

[Waldo Bastian]

On Saturday 24 December 2005 08:08, Thiago Macieira wrote:
> Koos Vriezen wrote:
> >Anyhow, point was that "people have to master more API" doesn't really
> >apply to application developers (and not using the lowlevel
> >send/process/..). I guess that in idl/.h files should also be the
> >interface name somewhere.
> >
> >Koos
>
> The problem I'm facing now is how to define which methods will be exposed
> through the DBUS channel.

Qt's meta model has a QMetaMethod::Scriptable qualifier that controls whether 
the method is exposed. I haven't figured out how it works, I guess there is 
some keyword that you can add and that is recognized by moc.

> First of all, I don't see how to set multiple interfaces in the same
> object so that they appear to have different methods externally.
>
> Second, I don't see a way of specifying which slots can be called
> externally. The bindings allow any slot to be called.
>
> Third, the bindings don't have yet any way of listing the available
> methods in an interface. I think all the information we need is already
> collected by moc (properties, signals and slots), so it would be possible
> to handle that at the binding level and generate the introspection format
> on the fly.

Yes, that's the first thing on the Qt-DBUS todo list I think.

> I have to investigate further.

Cheers,
Waldo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20051224/8cdf23bf/attachment.sig>