In https://bugs.freedesktop.org/show_bug.cgi?id=27175#c6 smcv wrote: """ ... TpMessage | \--- TpCMMessage (used by TpMessageMixin) \--- TpClientMessage (if needed, or just use the base class?) \--- TpSignalledMessage (or TpReceivedMessage, but it's used for MessageSent too) (has a TpContact for the sender if possible) \--- TpSavedMessage (the handle-less version, for the logger) ... """ We currently have TpMessage, TpCMMessage, TpClientMessage and TpSignalledMessage but not yet TpSavedMessage. I was porting Empathy to TpTextChannel was thinking that TpSavedMessage could actually be pretty handy in order to rebase EmpathyMessage on top of TpMessage.
Nicolas: What do you think about this? Would take make sense for tp-logger's API to expose message as TpSavedMessage?
(In reply to comment #1) > Nicolas: What do you think about this? Would take make sense for tp-logger's > API to expose message as TpSavedMessage? This would help to address bug 27174 (Make it possible to log composite messages). But it cannot replace the TplTextEvent as it cannot have TplEvent as base class. Maybe that would be provide by TplTextEvent in parallel with the simple _get_text() method ? Base on this, the only remaining utility is to give the logger the ability to create TpMessage (which is not easy atm).
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-glib/issues/64.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.