[Kde-pim] [PATCH] Export scriptable slots in AgentBase

Sebastian Trüg sebastian at trueg.de
Fri Oct 10 16:34:56 BST 2008


On Thursday 09 October 2008 14:38:28 Kevin Krammer wrote:
> On Thursday 09 October 2008, Sebastian Trüg wrote:
> > On Thursday 09 October 2008 12:13:20 Kevin Krammer wrote:
> > > On Wednesday 08 October 2008, Sebastian Trüg wrote:
> > > > May I commit the attached patch? It makes AgentBase export scriptable
> > > > slots. Thus, simple DBus interfaces can be created by marking slots
> > > > with Q_SCRIPTABLE.
> > >
> > > I am a bit worried that this might change how one of our standard
> > > interfaces look like at runtime introspection for that agent.
> > >
> > > Some D-Bus bindings create interface/proxy classes through
> > > introspection on first encounter and could end up with one that
> > > actually only applies to one specific agent not to all like it would
> > > suggest.
> > >
> > > I think you can still export the main object's slots without doing a
> > > separate adaptor by registering it a second time on a different path,
> > > i.e.
> > >
> > > QDBusConnection::sessionBus().resisterObject( "/AgentName", this,
> > > QDBusConnection::ExportScriptableSlots );
> >
> > hm, but can't the same thing happen if I just add another adaptor to the
> > class which is then exported automatically?
>
> No, another adaptor will become another D-Bus interface. I am just not sure
> if exporting slots of an object creates another D-Bus interface or if it
> adds it somewhere to an exisiting one.

It is exactly the same thing as with an adaptor: new interface, same object. 
That is why I don't get it.

Cheers,
Sebastian

_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/


More information about the kde-pim mailing list