Le Mercredi 15 Février 2006 20:36, Michaël Larouche a écrit : > This is a part of refactoring of Kopete4. > > Today, protocols can see more than a plain text for a status message. > Example is in MSN the NowListening thingy. Also in Jabber, the User Tune, > User Mood exists. Those are extended presence. > > So I made a first draft of Kopete::StatusMessage that encapsulate this. > It can contains the conventional text status message. But metadata can be > added to the message. > > I attached two patches. kopete_statusmessage_v1.patch.gz is the full diff > for the whole Kopete tree that include refactoring in NowListening plugin > and MSN plugin. > libkopete_statusmessage_v1.diff is for those that want a quick look on > Kopete::StatusMessage class and test, and additions to the Kopete API. > > Looking for inputs for your needs about this matter.
I like the idea. But there is for me 3 kind of message: A- the onlinestatus message (which change often, when you change your status) B- the personal message, or mood, (which change around once a day) C- the meta data (about the music played, .....) You covered nice the A and C , but not the B There is too much setOnlineStatus. and the B and C should not be in the setOnlineStatus. only A does matter. -- Olivier
pgp7uJlc1ymAJ.pgp
Description: PGP signature
_______________________________________________ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
