[Sugar-devel] [PATCH sugar-toolkit] Handle DBUS tubes in the activity telepathy client, part of OLPC #10738
sascha-ml-reply-to-2011-3 at silbe.org
Tue Jun 7 13:34:34 EDT 2011
Excerpts from Simon Schampijer's message of Mon May 30 14:41:59 +0200 2011:
> One part has to claim the interest into the dbus channels, either the
> Shell or the Activity. Before my patch sharing with dbus tubes did work,
> since the shell claimed that they would handle the channels, but this
> had the side effect of ghost invitations. Now I changed the code that
> the shell only approves invitations and the activity is responsible to
> handle/claim the channels they are interested in. Etoys (currently still
> using the presence service) will need to make the same, create a Handler
> that claims the channels Etoys is interested in .
OK, thanks, this makes things a little clearer, though there are still
one question I can't answer myself yet:
Do we need to change something in sugar-presence-service to make
activities that still rely on it (like EToys) work after your patches?
(we'll drop sugar-presence-service in 0.94, but not in 0.92.x)
There was another question I was going to ask re. Etoys compatibility,
but I noticed it's part of Glucose (etoys) / Fructose (Etoys), so we can
simply assume that matching versions of sugar-toolkit resp. Etoys will
be installed. We should point out the exact version relationships in
the Release Notes, of course.
I don't want to block these patches any further, so in the hope that
you'll write the Release Notes  entry explaining what non-Python
activity authors need to change I give my:
Acked-By: Sascha Silbe <silbe at activitycentral.com>
Your patches change the API, but AIUI there's no reasonable alternative.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 494 bytes
Desc: not available
More information about the Sugar-devel