| Summary: | Backlog messages do not go through message proccessor | ||
|---|---|---|---|
| Product: | [Unmaintained] telepathy | Reporter: | David Edmundson <kde> |
| Component: | text-ui | Assignee: | Telepathy Bugs <kde-telepathy-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ddomenichelli |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | Future | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
David Edmundson
2012-02-23 17:00:55 UTC
I suggest that we do it with 2 sets of filters, because we must show links and emoticons, but I wouldn't show, for example, a youtube video in the backlog @drdanz, I agree with that completely, but right now we only do links and emoticons so I'm happy for current code to go through the same set as it's simpler and would be identical. Then we split it out later when more plugins come (Hopefully a GSOC project so new development on this is currently paused.) Also when we implement this, I don't want to see multiple instances of the filters themselves (wasteful) or of MessageProcessor (as it's a singleton), we simply pass the message through varying different chains of MessageProcessor::m_filters. |