Bug 31768

Summary:	Provide a standard Text channel handler
Product:	Telepathy	Reporter:	Will Thompson <will>
Component:	tp-qt	Assignee:	Telepathy bugs list <telepathy-bugs>
Status:	RESOLVED MOVED	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	enhancement
Priority:	medium	CC:	ollisal
Version:	git master
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Will Thompson 2010-11-19 10:15:05 UTC

TelepathyQt4 should provide a standard implementation of a text channel handler. It should have a default constructor which gives you THT: Contact channels with MessageQueue and MessageSentSignal prepared (and maybe MessageCapabilities? I can't tell from its documentation what it does). We might want to have other constructors for specifying other features, and also a way to tweak the filter (so you can tell it you understand THT: Room and THT: None channels too).

I think it should default to Recover: True.

It should have a single signal, something like newTextChannel(Tp::TextChannelPtr).

(I've seen more than enough reimplementations of this for one lifetime.)

Comment 1 Will Thompson 2010-11-19 10:29:40 UTC

heh. I already filed this bug.

*** This bug has been marked as a duplicate of bug 28753 ***

Comment 2 Olli Salli 2011-03-08 01:27:20 UTC

I don't think this is a duplicate at all! Note: the old bug was about easily being an Observer for text channels. This is about being a Handler. I do, however, think that for ultimate API cleanliness the API for the other bug should stay as a single-contact (or all Contacts, but on 1-1 chats) API: membership is too important a concept in multi-user chats (unnamed and Room) to just discard it, but I'd not like to have signals for "this and this dude left / you were kicked / oh noes" in it either.

The simple text Handler for this bug should be usable for handling Room and unnamed group text chats too, though. But not give you any events besides receiving a Channel; the events should be received from the Channels.

Comment 3 Olli Salli 2011-03-08 01:29:31 UTC

And I DO agree that we need a family of Handler base-classes. Tube handlers (bugs #35084 and #35085) would be my first priority, though, as those are the most numerous kind of an application in the flying car future.

Comment 4 Olli Salli 2011-04-04 01:51:56 UTC

Some time ago I was contacted by Сергей Леви, who posted some text chat examples for tp-qt4 he had written. We should take a look at them to both serve as a basis for designing the Text channel handler utility class, and for creating a text chat example using that utility class.

The contributed examples are at http://dl.dropbox.com/u/247181/meego/lec05/telepathy-client.tar.gz.

Comment 5 GitLab Migration User 2019-12-03 20:27:58 UTC

-- 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-qt/issues/14.

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.