Gadget integration TODO: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
Line 14: Line 14:
Current work is in: http://monkey.collabora.co.uk/telepathy-gabble-gadget/
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.
* [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>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>
* <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>

Revision as of 08:19, 8 August 2008

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

Gadget

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
  • 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.
  • Implement Alias search
  • Gabble should close all the existing views if Gadget is disconnected

Presence Service

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

Sugar Toolkit

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

Sugar

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