647
edits
Changes
Jump to navigation
Jump to search
Line 36:
Line 36: − + Line 45:
Line 45: − + Line 55:
Line 55: − +
Development Team/Presence Service Removal (view source)
Revision as of 05:53, 8 March 2010
, 05:53, 8 March 2010no edit summary
* Present: Is fired when the properties contained in org.laptop.Telepathy.BuddyInfo become all non-None. We start tracking a BuddyInfo when it appears as online in the signal PresenceUpdate of org.freedesktop.Telepathy.Connection.Interface.Presence.
* Present: Is fired when the properties contained in org.laptop.Telepathy.BuddyInfo become all non-None. We start tracking a BuddyInfo when it appears as online in the signal PresenceUpdate of org.freedesktop.Telepathy.Connection.Interface.Presence.
* Future:
* Future: Listen contact list channels (Roster in the future) for the contacts we are subscribed to, and track their presence through the SimplePresence interface.
@dbus.service.signal(PRESENCE_INTERFACE, signature="o")
@dbus.service.signal(PRESENCE_INTERFACE, signature="o")
* Present: A buddy is known to have disappeared when PresenceUpdate notifies us it has gone offline.
* Present: A buddy is known to have disappeared when PresenceUpdate notifies us it has gone offline.
* Future:
* Future: Same as BuddyAppeared.
@dbus.service.signal(PRESENCE_INTERFACE, signature="oos")
@dbus.service.signal(PRESENCE_INTERFACE, signature="oos")
* Present: Gets fired when a new channel that communicates with a room becomes ready.
* Present: Gets fired when a new channel that communicates with a room becomes ready.
* Future:
* Future: Should be fired on reception of an incoming channel (TODO: check the API in MC5 for this)
@dbus.service.signal(PRESENCE_INTERFACE, signature="soos")
@dbus.service.signal(PRESENCE_INTERFACE, signature="soos")