Trac is being migrated to new services! Issues can be found in our new
YouTrack instance and WIKI pages can be found on our
website.
- Timestamp:
-
Feb 29, 2008, 10:47:21 AM (16 years ago)
- Author:
-
resiak
- Comment:
-
Add a Telepathy prpl project.
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v17
|
v18
|
|
46 | 46 | * Improve the widget-packing in a container (!GntBox), may be even have a grid-like container. |
47 | 47 | * Have a spell checker, which would add some way of indicating spelling errors, suggesting possible corrections, etc. |
| 48 | |
| 49 | == Telepathy prpl == |
| 50 | Currently, people wanting to use [http://telepathy.freedesktop.org Telepathy] have to switch from Pidgin to some other IM client (such as [http://live.gnome.org/Empathy Empathy]). It would be nice to have a Telepathy prpl for Pidgin, presumably based on the `telepathy-glib` client API (and possibly on `libmissioncontrol`). This would/could involve, depending on interest and time: |
| 51 | * Writing a prpl that speaks to Telepathy connection managers in order to connect IM accounts. |
| 52 | * Figuring out how to let accounts using that prpl be managed by Mission Control rather than by Pidgin, for coherence when using the rest of the Telepathy stack. |
| 53 | * Constructing some kind of global switch that makes Pidgin transparently use Telepathy rather than its own prpls when you flip it. |
| 54 | * Throwing together a hack to embed a `libempathy-gtk` video call widget into Pidgin when using the Telepathy prpl. |
| 55 | |
| 56 | Familiarity with D-Bus would be a plus here. You should either speak C, or enough of a ninja to write bindings for your favourite language in about seven seconds. |
| 57 | |
| 58 | (The astute will notice that this is the second half of last year's [wiki:Telepathy] SoC project, which there wasn't time to start on. Grab [wiki:resiak me] on IRC if you're interested.) |
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!