From: fmhess_at_[hidden]
Date: 2007-09-20 16:38:01
Author: fmhess
Date: 2007-09-20 16:38:00 EDT (Thu, 20 Sep 2007)
New Revision: 39426
URL: http://svn.boost.org/trac/boost/changeset/39426
Log:
Got rid of doxygen-generated main page, instead integrated
its content into boostbook docs (note I'm building them with
boostbook from sandbox/boost_docs now).
Removed:
sandbox/thread_safe_signals/libs/thread_safe_signals/doc/doxygen/
Text files modified:
sandbox/thread_safe_signals/libs/thread_safe_signals/doc/introduction.xml | 67 +++++++++++++++++++++++----------------
sandbox/thread_safe_signals/libs/thread_safe_signals/doc/signals.xml | 1
2 files changed, 41 insertions(+), 27 deletions(-)
Modified: sandbox/thread_safe_signals/libs/thread_safe_signals/doc/introduction.xml
==============================================================================
--- sandbox/thread_safe_signals/libs/thread_safe_signals/doc/introduction.xml (original)
+++ sandbox/thread_safe_signals/libs/thread_safe_signals/doc/introduction.xml 2007-09-20 16:38:00 EDT (Thu, 20 Sep 2007)
@@ -4,34 +4,47 @@
<section last-revision="$Date: 2007-06-12 14:01:23 -0400 (Tue, 12 Jun 2007) $">
<title>Introduction</title>
-<para>The Boost.Signals library is an implementation of a managed
-signals and slots system. Signals represent callbacks with multiple
-targets, and are also called publishers or events in similar
-systems. Signals are connected to some set of slots, which are
-callback receivers (also called event targets or subscribers), which
-are called when the signal is "emitted."</para>
+ <para>The Boost.Signals library is an implementation of a managed
+ signals and slots system. Signals represent callbacks with multiple
+ targets, and are also called publishers or events in similar
+ systems. Signals are connected to some set of slots, which are
+ callback receivers (also called event targets or subscribers), which
+ are called when the signal is "emitted."</para>
-<para>Signals and slots are managed, in that signals and slots (or,
-more properly, objects that occur as part of the slots) can track
-connections and are capable of automatically disconnecting signal/slot
-connections when either is destroyed. This enables the user to make
-signal/slot connections without expending a great effort to manage the
-lifetimes of those connections with regard to the lifetimes of all
-objects involved.</para>
+ <para>Signals and slots are managed, in that signals and slots (or,
+ more properly, objects that occur as part of the slots) can track
+ connections and are capable of automatically disconnecting signal/slot
+ connections when either is destroyed. This enables the user to make
+ signal/slot connections without expending a great effort to manage the
+ lifetimes of those connections with regard to the lifetimes of all
+ objects involved.</para>
-<para>When signals are connected to multiple slots, there is a
-question regarding the relationship between the return values of the
-slots and the return value of the signals. Boost.Signals allows the
-user to specify the manner in which multiple return values are
-combined.</para>
-
-<para>This documentation describes a thread-safe variant of the
-official Boost.Signals library. There have been some changes to
-the interface to support thread-safety, mostly with respect to
-automatic connection management. This implementation was written by
-Frank Mori Hess. Acknowledgements are also due to Timmo Stange, Peter
-Dimov, and Gottlob Frege for ideas and feedback, and to Douglas Gregor
-for the original version of Boost.Signals this effort was based on.
-</para>
+ <para>When signals are connected to multiple slots, there is a
+ question regarding the relationship between the return values of the
+ slots and the return value of the signals. Boost.Signals allows the
+ user to specify the manner in which multiple return values are
+ combined.</para>
+ <section>
+ <title>thread_safe_signals</title>
+ <para>This documentation describes a thread-safe variant of the
+ official Boost.Signals library. There have been some changes to
+ the interface to support thread-safety, mostly with respect to
+ automatic connection management. This implementation was written by
+ Frank Mori Hess. Acknowledgements are also due to Timmo Stange, Peter
+ Dimov, and Gottlob Frege for ideas and feedback, and to Douglas Gregor
+ for the original version of Boost.Signals this effort was based on.
+ </para>
+ </section>
+ <section>
+ <title>Download</title>
+ <para>The latest release is available from the <ulink url="http://www.boost-consulting.com/vault/index.php?&direction=0&order=&directory=thread_safe_signals">Boost vault</ulink>.
+ The development version of the code is available in the sandbox of the
+ <ulink url="http://svn.boost.org/trac/boost/wiki/BoostSubversion">Boost svn</ulink>.
+ The files for thread_safe_signals are located in the <code>sandbox/thread_safe_signals</code>
+ subdirectory and may be <ulink url="http://svn.boost.org/trac/boost/browser/sandbox/thread_safe_signals">
+ browsed online</ulink> or checked out with the following command:
+ <programlisting>svn co http://svn.boost.org/svn/boost/sandbox/thread_safe_signals thread_safe_signals</programlisting>
+ </para>
+ </section>
</section>
\ No newline at end of file
Modified: sandbox/thread_safe_signals/libs/thread_safe_signals/doc/signals.xml
==============================================================================
--- sandbox/thread_safe_signals/libs/thread_safe_signals/doc/signals.xml (original)
+++ sandbox/thread_safe_signals/libs/thread_safe_signals/doc/signals.xml 2007-09-20 16:38:00 EDT (Thu, 20 Sep 2007)
@@ -12,6 +12,7 @@
</author>
<author>
<firstname>Frank</firstname>
+ <othername>Mori</othername>
<surname>Hess</surname>
<!-- <email>fmhess_at_[hidden]</email> -->
</author>