[telepathy-doc/master] More on Presence
Danielle Madeley
danielle.madeley at collabora.co.uk
Fri Sep 18 01:40:31 PDT 2009
---
docs/book/C/accounts.xml | 139 +++++++++++++++++++++++++++---------
docs/book/C/channel-dispatcher.xml | 12 ++--
docs/book/C/connection.xml | 3 +-
3 files changed, 113 insertions(+), 41 deletions(-)
diff --git a/docs/book/C/accounts.xml b/docs/book/C/accounts.xml
index 26ef54a..c808225 100644
--- a/docs/book/C/accounts.xml
+++ b/docs/book/C/accounts.xml
@@ -324,40 +324,111 @@
</para>
</tip>
- <table id="table.sect.accounts.presence.Connection-Presence-Type">
- <title>Status Types (Connection_Presence_Type)</title>
- <tgroup cols="2">
- <thead>
- <row>
- <entry>Online Statuses</entry>
- <entry>Offline Statuses</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>Available</entry>
- <entry>Offline</entry>
- </row>
- <row>
- <entry>Away</entry>
- <entry></entry>
- </row>
- <row>
- <entry>Extended_Away</entry>
- <entry></entry>
- </row>
- <row>
- <entry>Hidden</entry>
- <entry></entry>
- </row>
- <row>
- <entry>Busy</entry>
- <entry></entry>
- </row>
- </tbody>
- </tgroup>
- </table>
-
+ <sect2 id="sect.accounts.presence.going-online">
+ <title>Going Online</title>
+
+ <sect3 id="sect.accounts.presence.going-online.on-request">
+ <title>On Request</title>
+
+ <para>
+ Mission Control will attempt to connect any enabled account that has a
+ <property>RequestedPresence</property> other than
+ <type>Connection_Presence_Type_Offline</type>.
+ </para>
+
+ <para>
+ Bringing an <interfacename>Account</interfacename> online in the
+ Account Manager simply requires setting the presence via
+ <property>RequestedPresence</property> to a presence that
+ requires being online (see
+ <xref linkend="table.sect.accounts.presence.Connection-Presence-Type"/>).
+ </para>
+
+ <para>
+ For example, to make an account be connected, you might set the presence
+ (<type>Connection_Presence_Type_Available</type>, "available", "Working
+ Hard"). You can watch the properties <property>Connection</property>,
+ <property>ConnectionStatus</property>,
+ <property>ConnectionStatusReason</property> and
+ <property>CurrentPresence</property> to monitor the state of the new
+ connection via the signal
+ <methodname>AccountPropertyChanged</methodname>.
+ </para>
+
+ <table id="table.sect.accounts.presence.Connection-Presence-Type">
+ <title>Status Types (Connection_Presence_Type)</title>
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry>Online Statuses</entry>
+ <entry>Offline Statuses</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>Available</entry>
+ <entry>Offline</entry>
+ </row>
+ <row>
+ <entry>Away</entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>Extended_Away</entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>Hidden</entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>Busy</entry>
+ <entry></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ <para>
+ To disconnect an account for any reason, simply set its status to
+ Offline with the presence
+ (<type>Connection_Presence_Type_Offline</type>, "offline", "").
+ </para>
+ </sect3>
+
+ <sect3 id="sect.accounts.presence.going-online.on-demand">
+ <title>On Demand</title>
+
+ <para>
+ Enabled accounts can be brought online automatically at the request of
+ the <link linkend="chapter.channel-dispatcher">Channel Dispatcher</link>
+ to service a new channel request.
+ </para>
+
+ <para>
+ This is done by setting the current value for
+ <property>AutomaticPresence</property> as the
+ <property>RequestedPresence</property>.
+ </para>
+ </sect3>
+
+ <sect3 id="sect.accounts.presence.going-online.automatic">
+ <title>Automatically</title>
+
+ <para>
+ Enabled accounts with the <property>ConnectAutomatically</property>
+ property set are brought online automatically by the Account Manager
+ without any action required on the part of the user or other software.
+ </para>
+
+ <para>
+ This is done by setting the current value for
+ <property>AutomaticPresence</property> as the
+ <property>RequestedPresence</property>.
+ </para>
+ </sect3>
+
+ </sect2>
</sect1>
<!-- para>TODO:
Notes:
diff --git a/docs/book/C/channel-dispatcher.xml b/docs/book/C/channel-dispatcher.xml
index fb6f284..180309c 100644
--- a/docs/book/C/channel-dispatcher.xml
+++ b/docs/book/C/channel-dispatcher.xml
@@ -64,12 +64,12 @@
<para>
The Channel Dispatcher watches the
- <link xref="chapter.connection">Connections</link> known to the
- <link xref="chapter.accounts">Account Manager</link> and keeps track of what
- <link xref="sect.channel-dispatcher.clients">Clients</link> are available
- to handle incoming Channels from those Connections. When a new channel
- comes in, the Channel Dispatcher looks at the available clients, and the
- types of channels they handle and then selects clients to dispatch the
+ <link linkend="chapter.connection">Connections</link> known to the
+ <link linkend="chapter.accounts">Account Manager</link> and keeps track of
+ what <link linkend="sect.channel-dispatcher.clients">Clients</link> are
+ available to handle incoming Channels from those Connections. When a new
+ channel comes in, the Channel Dispatcher looks at the available clients, and
+ the types of channels they handle and then selects clients to dispatch the
channel to.
</para>
diff --git a/docs/book/C/connection.xml b/docs/book/C/connection.xml
index 41f0d7c..1b5aad0 100644
--- a/docs/book/C/connection.xml
+++ b/docs/book/C/connection.xml
@@ -252,7 +252,8 @@
<property>AutomaticPresence</property>.
</para>
<para>
- See ...
+ See <xref linkend="sect.accounts.presence.going-online.on-demand"/>
+ for more information.
</para>
</tip>
--
1.5.6.5
More information about the telepathy-commits
mailing list