Le mercredi 10 octobre 2007, Matt Rogers a écrit : > On Wed, Oct 10, 2007 at 11:21:16AM -0400, Micha??l Larouche wrote: > > I started in a local git branch the new public D-Bus API for Kopete > > > > In this email I attached the C++ header which implement the D-Bus > > interface and the xml generated by qdbuscpp2xml. > > > > The current interface is fairy basic and it's close to the older DCOP > > interface, though much cleaner. It still need improvement. > > it is also using MetaContact display name to reference a contact because > > it is the simpliest way to address contacts for KDE 4.0. > > > > I need feedback on the interface and also I need to know if I can > > include this into KDE 4.0. That would be sad to ship Kopete without a > > D-Bus interface. > > So I thought about this a bit more and I'm wondering why we need a > separate interface for d-bus when we can have Kopete::ContactList > export its various signals and slots as needed.
Kopete::ContactList manages pointers to internals classes (Kopete::MetaContact , Kopete::Contact, Kopete::OnlineStatus ) Dbus application can only work with (strings) identifiers Just a thought about the interface: The idea is to allow to have several status per identity, so you could add an identity argument to method that set status or message.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel
