Bug 24851 - Decide once and for all whether chat states are ever useful on non-text channels
Summary: Decide once and for all whether chat states are ever useful on non-text channels
Status: RESOLVED FIXED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-spec (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Simon McVittie
QA Contact: Telepathy bugs list
URL: http://git.collabora.co.uk/?p=user/sm...
Whiteboard: specmeet+
Keywords: patch
Depends on:
Blocks:
 
Reported: 2009-11-02 06:19 UTC by Andre Moreira Magalhaes
Modified: 2009-11-12 05:54 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Andre Moreira Magalhaes 2009-11-02 06:19:12 UTC 
Chat states as of now requires that a channel implements the Channel interface only, we should decide once and for all whether chat states are ever useful on non-text channels

As a side note, in Telepathy-Qt4 chat states high-level API is specific to text channels
Comment 1 Simon McVittie 2009-11-02 06:27:36 UTC 
(In reply to comment #0)
> As a side note, in Telepathy-Qt4 chat states high-level API is specific to text
> channels

If we decide that ChatStates *is* useful on non-Text channels, then telepathy-qt4 can break ABI for 0.4 to move this functionality to Channel, and until then, people who need chat states on non-Text channels (both of them :-) can use the auto-generated client code instead of the high-level API.
Comment 2 Simon McVittie 2009-11-05 08:22:14 UTC 
Rob declares that we were wrong to allow ChatStates on non-Text, and tp-qt4 is right. Assigning to myself to XML it.
Comment 3 Simon McVittie 2009-11-06 11:55:36 UTC 
Specmeet-approved and drafted. Someone review the spec wording, please?
Comment 4 Simon McVittie 2009-11-12 05:54:14 UTC 
Fixed in master, will be in 0.19.0

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.