From kde-telepathy Mon Jan 21 07:54:26 2013 From: Martin Klapetek Date: Mon, 21 Jan 2013 07:54:26 +0000 To: kde-telepathy Subject: Metacontacts/KPeople status Message-Id: X-MARC-Message: https://marc.info/?l=kde-telepathy&m=135875491830880 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============4302236274138381543==" --===============4302236274138381543== Content-Type: multipart/alternative; boundary=90e6ba613aba0645fa04d3c7c7cc --90e6ba613aba0645fa04d3c7c7cc Content-Type: text/plain; charset=UTF-8 Hey everyone, here's how it currently looks with our metacontacts. KPeople is fully usable now. The API as well as the code needs some cleanup, but right now everything we want is there and working. Overview: * grouping/ungrouping contacts (even with non-IM contacts) * starting chats/audio/video * getting detailed info about persons What's missing * editing stuff - this is very easy in terms of code, but becomes quite complex in the bigger picture; we need writeback services in Nepomuk in order for this to work sensibly. Right now we're getting data from Akonadi and Telepathy. If we change say a nickname in contact list (with kpeople), this change should be written back to Telepathy. Same goes for Akonadi of course. Otherwise we're in a state where two data providers have inconsistent data and that can lead to problems. OR we can do all changes only locally in Nepomuk. What's bad about that is that the changes will be kept only locally. On the other hand, the grouping into metacontacts will also be just local. Vishesh, what's your take on this? * filtering & sorting - we have a plan with David to have shared roles between models, so we can switch models on the fly. Once we achieve that, we'll reuse the current (awesome) proxy filter * starting actions through KTp infrastructure - this is again so we can just switch the models on the fly and thus reuse all the existing KTp code paths. However one tiny issue is that we don't have account info accessible in the main KPeople model. I'm thinking * grouping - should be fairly easy, the groups are present in Nepomuk, just not used * contact's offline presence - for the contact list to work properly with kpeople, one needs to have the ktp-nepomuk-feeder running ALL the time. Once it's down, we're screwed. Currently there's a different problem though - when the service shuts down (logout or reboot for example), it leaves all the presences in Nepomuk in whatever state they were. This means when you relogin and run the contact list, all the contacts have wrong presences until the feeder kicks in and puts correct data into Nepomuk. If the feeder for whatever reason won't start, the user is left with random invalid presences. It could write offline presence while being destroyed, but that would need to be synchronous job which can take some time, which means delaying reboot/logout/whatever for no apparent/visible reason to the user. We were talking if we could reuse KTp presences as we have them available in almost realtime, but that means combining two models (where one queries the other) and I don't like that very much. * good looking delegate for metacontacts - right now I'm simply painting the presences in a row with no indication of "this is a metacontact" (except the multiple presences on one row). Double-clicking the item expands it and shows all the individual contacts. Ideas/mockups welcome. * good startup time - currently we're at ~3 secs before contact list shows up with ~800 contacts. I'll investigate where's the holdup and see what we can do about it. If we can get at least the last 4 tasks sorted (plus filtering), I'm very happy to ship it with 0.6 as a tech-preview. The metacontacts users create in this should prevail once we get the full thing released. The development is happening in branches - kde:libkpeople - mklapetek/toplevel_contacts and kde:ktp-contact-list - mklapetek/kpeople. I'll spend this week on cleaning up kpeople and tuning the performance. If you'd like to help out, let me know and I'll point out exactly what needs doing. Cheers -- Martin Klapetek | KDE Developer --90e6ba613aba0645fa04d3c7c7cc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hey everyone,

here's how it currently loo= ks with our metacontacts. KPeople is fully usable now. The API as well as t= he code needs some cleanup, but right now everything we want is there and w= orking.

Overview:
=C2=A0* grouping/ungrouping contact= s (even with non-IM contacts)
=C2=A0* starting chats/audio/video<= /div>
=C2=A0* getting detailed info about persons

<= div>What's missing
=C2=A0* editing stuff
- this is very easy in terms of code, but becomes= quite complex in the bigger picture; we need writeback services in Nepomuk= in order for this to work sensibly. Right now we're getting data from = Akonadi and Telepathy. If we change say a nickname in contact list (with kp= eople), this change should be written back to Telepathy. Same goes for Akon= adi of course. Otherwise we're in a state where two data providers have= inconsistent data and that can lead to problems. OR we can do all changes = only locally in Nepomuk. What's bad about that is that the changes will= be kept only locally. On the other hand, the grouping into metacontacts wi= ll also be just local. Vishesh, what's your take on this?
=C2=A0* filtering & sorting
- we have a plan with Davi= d to have shared roles between models, so we can switch models on the fly. = Once we achieve that, we'll reuse the current (awesome) proxy filter
=C2=A0* starting actions through KTp infrastructure
=
- this= is again so we can just switch the models on the fly and thus reuse all th= e existing KTp code paths. However one tiny issue is that we don't have= account info accessible in the main KPeople model. I'm thinking
=C2=A0* grouping
- should be fairly easy, the groups are p= resent in Nepomuk, just not used
=C2=A0* contact'= ;s offline presence
- for = the contact list to work properly with kpeople, one needs to have the ktp-n= epomuk-feeder running ALL the time. Once it's down, we're screwed. = Currently there's a different problem though - when the service shuts d= own (logout or reboot for example), it leaves all the presences in Nepomuk = in whatever state they were. This means when you relogin and run the contac= t list, all the contacts have wrong presences until the feeder kicks in and= puts correct data into Nepomuk. If the feeder for whatever reason won'= t start, the user is left with random invalid presences. It could write off= line presence while being destroyed, but that would need to be synchronous = job which can take some time, which means delaying reboot/logout/whatever f= or no apparent/visible reason to the user. We were talking if we could reus= e KTp presences as we have them available in almost realtime, but that mean= s combining two models (where one queries the other) and I don't like t= hat very much.
=C2=A0* good looking delegate for metacontacts
- right now= I'm simply painting the presences in a row with no indication of "= ;this is a metacontact" (except the multiple presences on one row). Do= uble-clicking the item expands it and shows all the individual contacts. Id= eas/mockups welcome.
=C2=A0* good startup time
- currently we're at ~3 secs= before contact list shows up with ~800 contacts. I'll investigate wher= e's the holdup and see what we can do about it.

If we can get at least the last 4 tasks so= rted (plus filtering), I'm very happy to ship it with 0.6 as a tech-pre= view. The metacontacts users create in this should prevail once we get the = full thing released.

The development is happening in branches - kde:libkpeop= le - mklapetek/toplevel_contacts and kde:ktp-contact-list - mklapetek/kpeop= le. I'll spend this week on cleaning up kpeople and tuning the performa= nce.

If you'd like to help out, let me know and I'll= point out exactly what needs doing.

Cheers
-= -
Martin Klapetek | KDE=C2= =A0Developer
--90e6ba613aba0645fa04d3c7c7cc-- --===============4302236274138381543== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ KDE-Telepathy mailing list KDE-Telepathy@kde.org https://mail.kde.org/mailman/listinfo/kde-telepathy --===============4302236274138381543==--