[Sugar-devel] [PATCH sugar-toolkit] Fix invitations from a non sugar client (empathy), part of OLPC #10814
simon at schampijer.de
Mon May 23 11:49:53 EDT 2011
On 05/23/2011 04:21 PM, Bert Freudenberg wrote:
> On 23.05.2011, at 16:04, Simon Schampijer wrote:
>> On 04/16/2011 01:34 PM, Sascha Silbe wrote:
>>> Excerpts from Simon Schampijer's message of Thu Apr 14 19:43:20 +0200 2011:
>>>> This differentiates between sugar and non sugar invitations using the
>>>> handle type. For non-sugar invitations we use the activity id to
>>>> determine which activity to join.
>>> How exactly does this work? Who creates the Activity object in
>>> Telepathy that we access using get_activity() / GetActivity()? Is
>>> self._activity_id the usual UUID string or some special value?
>>> Is there any documentation for the Activity API in Telepathy? The
>>> Telepathy spec  doesn't even contain a single mention.
>>>  http://telepathy.freedesktop.org/spec/
>> It is the same UUID. We have been using the Activity-ID for that purpose since the beginning.
>> We use the activity-id when we join an activity. We let telepathy know when we share the activity .
>> Best is to look in extensions/extensions.html in telepathy-salut or telepathy-gabble, there you find AddActivity for example.
> You mean here?
> Interesting, I was not aware there was OLPC/Sugar-specific stuff in Telepathy itself.
> - Bert -
In theory yes - but I guess you have to build it to get
extensions/extensions.html (found it here in jhbuild).
More information about the Sugar-devel