| Summary: | Check Channel.Text for deprecated stuff now that Messages is mandatory | ||
|---|---|---|---|
| Product: | Telepathy | Reporter: | Andre Moreira Magalhaes <andrunko> |
| Component: | tp-qt | Assignee: | Telepathy bugs list <telepathy-bugs> |
| Status: | RESOLVED MOVED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
| Severity: | normal | ||
| Priority: | medium | CC: | ollisal |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Bug Depends on: | |||
| Bug Blocks: | 33115 | ||
|
Description
Andre Moreira Magalhaes
2011-01-14 08:54:09 UTC
The Tp::TextChannel API completely hides the differences between bare Chan.Type.Text and Chan.I.Messages enabled Text channels, so I don't see how this affects tp-qt4 exactly? Or are you proposing we remove the fallback support for the legacy Text interface from the implementation side? Andre: What do you mean? Do you think we need actual Tp::TextChannel deprecations (public API concepts which don't make sense with Messages), or not? Otherwise, let's INVALID this. -- 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/16. |
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.