Gadget integration TODO

Things to do to integrate Gadget with the rest of the system.

Gadget

• Should not return himself in buddy queries (and probably not activities which we are already taking part in activity queries).
• Correctly manage size of open views
• Support buddy views properly
• Add CurrentActivity protocol
• re-review and merge http://dev.laptop.org/git?p=users/guillaume/gadget;a=shortlog;h=activity
• Text search

Gabble

Current work is in: http://monkey.collabora.co.uk/telepathy-gabble-gadget/

• Start to review this big branch. Be aware that the first set of patches is very old (prior Gadget implementation) so it could be a bit outdated.
• BuddyInfo.GetActivity should return activities from view
• Because of this ejabberd bug, client still use PEP nodes instead of just rely on Gadget. We should be sure everything works fine when this bug will be fixed.
• Implement "search from text input"
• Manage BuddyInfo current-activity from views
• When receiving a buddy properties change message, we should update properties stored in views
• Handle join and left messages
• Fire BuddyInfo.ActivitiesChanged when needed

Presence Service

Current work is in: https://dev.laptop.org/git?p=users/guillaume/presence-service;a=shortlog;h=gadget

• The inspector shouldn't appear as an activity member. When sharing a Connect instance, the inspector joins the room so we are suppose to play with it.
• The SearchAvailable signal is a bit crack. Would be cool to drop it.
• Because of this ejabberd bug, client still use PEP nodes instead of just rely on Gadget. We should be sure everything works fine when this bug will be fixed.
• Extend D-Bus API for search queries. See Presence Service D-Bus API

Sugar Toolkit

Current work is in: https://dev.laptop.org/git?p=users/guillaume/sugar-toolkit;a=shortlog;h=gadget

• Implement missing methods

Sugar

Current work is in: https://dev.laptop.org/git?p=users/guillaume/sugar;a=shortlog;h=gadget

• This branch is currently just used for tests. Sugar requests 10 random activities in MeshModel.py, that's probably not the best place to do that.
• Make the number of random buddies and activities requested configurable
• Implement UI for searches (not a priority as for now we'll focus on random queries)