Gadget integration TODO: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
No edit summary
 
(19 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Things to do to integrate [[Gadget]] with the rest of the system.
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).
* <strike>Correctly manage size of open views</strike>
* <strike>Support buddy views properly</strike>
* <strike>Add CurrentActivity protocol</strike>
* Buddy search on alias
* Text search
* Test Gadget with OpenFire once [http://www.igniterealtime.org/community/message/175507 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.
* <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>

== Presence Service ==

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

* [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.
* 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.
* 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

* [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]
* Implement missing methods


== Sugar ==
== Sugar ==


* Should track change of the "publish to gadget" GConf key and call Publish when needed ([http://dev.laptop.org/ticket/7544 #7544])
Current work is in: https://dev.laptop.org/git?p=users/guillaume/sugar;a=shortlog;h=gadget

* [https://dev.laptop.org/ticket/7545 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
* 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)
* [https://dev.laptop.org/ticket/7711 Implement UI for searches]


[[Category:Telepathy]]
[[Category:Telepathy]]

Latest revision as of 14:55, 24 October 2008

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

Sugar

  • Should track change of the "publish to gadget" GConf key and call Publish when needed (#7544)
  • Make the number of random buddies and activities requested configurable
  • Implement UI for searches