Gadget integration TODO: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 14: | Line 14: | ||
* Shouldn't ignore buddy handles from views. So should either: |
* Shouldn't ignore buddy handles from views. So should either: |
||
** Merge the fix of [https://dev.laptop.org/ticket/8444 #8444 (Ignoring handles which are not in roster drop buddies from shared roster)] |
** Merge the fix of [https://dev.laptop.org/ticket/8444 #8444 (Ignoring handles which are not in roster drop buddies from shared roster)] |
||
** Track views in PS and check if the handle is in one of the views. |
|||
== Sugar == |
== Sugar == |
||
Revision as of 16:25, 22 October 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).
- Test Gadget with OpenFire once this bug is fixed
Gabble
- Review the view presence branch.
Presence Service
- Shouldn't ignore buddy handles from views. So should either:
- Merge the fix of #8444 (Ignoring handles which are not in roster drop buddies from shared roster)
- Track views in PS and check if the handle is in one of the views.
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)