On October 10, 2007 05:19:05 pm Matt Rogers wrote: > 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.
I don't think it would be a good design decision to add some methods to Kopete::ContactList just to add some method to the D-Bus interface which are not related to ContactList. I'm thinking about setIdentity*, setStatus, setStatusMessage. I think we can narrow down more easily the functionality of the API using a dedicated class for D-Bus API. Like the Facade and Proxy design pattern. -- Michaël Larouche KDE develope -------------------------------------- Website: http://www.tehbisnatch.org/ MSN: [EMAIL PROTECTED] IRC: irc.freenode.org/DarkShock Jabber/email: [EMAIL PROTECTED] _______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel
