#10738 NORM 11.2.0-: Salut: when joining a shared activity an invitation palette is added

[Zarro Boogs per Child]

#10738: Salut: when joining a shared activity an invitation palette is added
------------------------------+---------------------------------------------
           Reporter:  erikos  |       Owner:  erikos                           
               Type:  defect  |      Status:  new                              
           Priority:  normal  |   Milestone:  11.2.0-M4                        
          Component:  sugar   |     Version:  Development build as of this date
         Resolution:          |    Keywords:  collaboration                    
        Next_action:  code    |    Verified:  0                                
Deployment_affected:          |   Blockedby:                                   
           Blocking:          |  
------------------------------+---------------------------------------------

Comment(by erikos):

 More diagnosis on this one:

 We have two places where channels are handled with a
 [http://telepathy.freedesktop.org/doc/book/sect.channel-
 dispatcher.clients.html#sect.channel-dispatcher.clients.impl.handler
 Telepathy Client]:

 - the [http://git.sugarlabs.org/sugar/mainline/blobs/master/src/ja\
 rabe/model/telepathyclient.py#line61 shell] is one place, the shell
 actually claims to be interested in all channels

 - [activities http://git.sugarlabs.org/sugar-
 toolkit/mainline/blobs/master/s\
 rc/sugar/activity/activity.py#line909] can be handlers as well, the
 activity does not claim to be interested in dbus tube channels

 If we remove the the interest in the dbus tubes from the
 'HandlerChannelFilter' in the shell the activities do not get any dbus
 tube channels anymore (can be tested with Memorize). Adding the interest
 into dbus tube channels to the 'HandlerChannelFilter' in the activity we
 do get the dbus channels in the activity. Actually we do not need to do
 anything with the channels, just claiming we handle them is enough, that
 is why it worked to claim them as well from the shell. I think the
 activity is the better place to handle the claim, though.

-- 
Ticket URL: <http://dev.laptop.org/ticket/10738#comment:6>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system