KTp/Tasks/Metacontacts: Difference between revisions

From KDE Community Wiki
< KTp‎ | Tasks
Line 23: Line 23:
I think everything will be pretty much the same "all people" or "give me a person with this ID", now let me do telepathy things.
I think everything will be pretty much the same "all people" or "give me a person with this ID", now let me do telepathy things.


=== Original Plan ===
=== Main Plan ===
 
This is a copy of George G's plan
 
http://grundleborg.wordpress.com/2011/04/26/kde-telepathy-a-vision-for-integration/
 
In short:
- A nepomuk service monitors KDE Telepathy.
- Syncs ALL telepathy data into pimo::contacts
- These have relationships to make PIMO::Persons
- We have a library that pulls stuff out of nepomuk and is the basis of the contact list.
- Tp::Contacts are looked up in the client library from the PIMO::Person.
- All actions are handled inside the client library (start chats etc)


=== KPeople===
=== KPeople===


=== Dave's Proposed Mods ===
=== Dave's Proposed Mods ===

Revision as of 21:58, 21 February 2012

Metacontacts

Goals

* Merge contacts from various contacts (i.e same person on Facebook + Jabber) appear as one entry in the list.
* Still see individual contact information, start chats with contacts.
* From within a chat, select a different account to talk to the same person.
* Optionally show names/avatar from KDE PIM sources as well as Tp.
* KDE Telepathy needs to STILL WORK when nepomuk is disabled, but I'm happy for it to not have metacontact support etc.

Library Use Cases

Contact List

We need a model of all people, with child nodes for each contact.

Handlers

From a handler (text-ui) POV we need to be able to get a person from an individual Tp::Contact. This should NOT load the entire model then search for the correct person.

Outside KTelepathy

I think everything will be pretty much the same "all people" or "give me a person with this ID", now let me do telepathy things.

Main Plan

This is a copy of George G's plan

http://grundleborg.wordpress.com/2011/04/26/kde-telepathy-a-vision-for-integration/

In short:

- A nepomuk service monitors KDE Telepathy.
- Syncs ALL telepathy data into pimo::contacts
- These have relationships to make PIMO::Persons
- We have a library that pulls stuff out of nepomuk and is the basis of the contact list.
- Tp::Contacts are looked up in the client library from the PIMO::Person. 
- All actions are handled inside the client library (start chats etc)

KPeople

Dave's Proposed Mods