Gadget integration TODO: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 27: | Line 27: | ||
* [https://dev.laptop.org/ticket/7542 #7542 (Gadget integration)] |
* [https://dev.laptop.org/ticket/7542 #7542 (Gadget integration)] |
||
* <strike>Properly manage activity and buddy views</strike> |
* <strike>Properly manage activity and buddy views</strike> |
||
* 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. |
* <strike>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.</strike> |
||
* The SearchAvailable signal is a bit crack. Would be cool to drop it. |
* The SearchAvailable signal is a bit crack. Would be cool to drop it. |
||
* Because of [https://support.process-one.net/browse/EJAB-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel 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. |
* Because of [https://support.process-one.net/browse/EJAB-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel 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. |
||
Revision as of 09:01, 18 July 2008
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
- 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 viewsWhen receiving a buddy properties change message, we should update properties stored in viewsHandle join and left messagesFire BuddyInfo.ActivitiesChanged when needed
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 viewsThe 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
- 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)