Gadget integration TODO
Jump to navigation
Jump to search
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 viewsSupport buddy views properlyAdd CurrentActivity protocolBuddy search on alias- Text search
- Test Gadget with OpenFire once this bug is fixed
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 viewBecause 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 viewsWhen receiving a buddy properties change message, we should update properties stored in viewsHandle join and left messagesFire BuddyInfo.ActivitiesChanged when neededThe 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.Implement Alias search
Presence Service
Current work is in: https://dev.laptop.org/git?p=users/guillaume/presence-service;a=shortlog;h=gadget
- #7542 (Gadget integration)
Properly manage activity and buddy views- The SearchAvailable signal is a bit crack. Would be cool to drop it.
- 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
- sugar-toolkit: wrap Gadget new PS API
- sugar-toolkit: Add a "Publish" option to sugar profile
- Implement missing methods
Sugar
Current work is in: https://dev.laptop.org/git?p=users/guillaume/sugar;a=shortlog;h=gadget
- Should request random activities/buddies to populate the mesh view
- 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)