Gadget integration TODO: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
== Gadget == |
== Gadget == |
||
* [https://dev.laptop.org/ticket/7816 Should not return himself in buddy queries (and probably not activities which we are already taking part in activity queries).] |
* [https://dev.laptop.org/ticket/7816 Should not return himself in buddy queries (and probably not activities which we are already taking part in activity queries).] |
||
* <strike>Correctly manage size of open views</strike> |
|||
* <strike>Support buddy views properly</strike> |
|||
* <strike>Add CurrentActivity protocol</strike> |
|||
* <strike>Buddy search on alias</strike> |
|||
* [https://dev.laptop.org/ticket/7817 Text search] |
|||
* Test Gadget with OpenFire once [http://www.igniterealtime.org/community/message/175507 this bug] is fixed |
* Test Gadget with OpenFire once [http://www.igniterealtime.org/community/message/175507 this bug] is fixed |
||
== Gabble == |
== Gabble == |
||
Current work is in: http://monkey.collabora.co.uk/telepathy-gabble-gadget/ |
|||
* Review the [http://monkey.collabora.co.uk/telepathy-gabble_presence-aggregator-rebased/ view presence] branch. |
|||
* [https://dev.laptop.org/ticket/7868 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. |
|||
* <strike>BuddyInfo.GetActivity should return activities from view</strike> |
|||
* <strike>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.</strike> |
|||
* Implement "search from text input" |
|||
* <strike>Manage BuddyInfo current-activity from views</strike> |
|||
* <strike>When receiving a buddy properties change message, we should update properties stored in views</strike> |
|||
* <strike>Handle join and left messages</strike> |
|||
* <strike>Fire BuddyInfo.ActivitiesChanged when needed</strike> |
|||
* <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> |
|||
* <strike>Implement Alias search</strike> |
|||
* <strike>Gabble should close all the existing views if Gadget is disconnected</strike> |
|||
== Presence Service == |
== Presence Service == |
||
| Line 31: | Line 16: | ||
* [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> |
|||
* The SearchAvailable signal is a bit crack. Would be cool to drop it. |
|||
* <strike>Extend D-Bus API for search queries. See [[Presence Service D-Bus API]]</strike> |
|||
* Implement "search from text input" |
|||
== Sugar Toolkit == |
|||
Current work is in: https://dev.laptop.org/git?p=users/guillaume/sugar-toolkit;a=shortlog;h=gadget |
|||
* [https://dev.laptop.org/ticket/7543 sugar-toolkit: wrap Gadget new PS API] |
|||
* [https://dev.laptop.org/ticket/7544 sugar-toolkit: Add a "Publish" option to sugar profile] |
|||
* Wrap "search from text input" |
|||
== Sugar == |
== Sugar == |
||
Revision as of 16:21, 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
Current work is in: https://dev.laptop.org/git?p=users/guillaume/presence-service;a=shortlog;h=gadget
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)