*** empty log message ***

3 files changed, 40 insertions, 56 deletions

diff --git a/docs/ACE-tutorials.html b/docs/ACE-tutorials.html
index 0465b2562d6..c6c1a259cf9 100644
--- a/docs/ACE-tutorials.html
+++ b/docs/ACE-tutorials.html
@@ -6,14 +6,26 @@
 
 The <A HREF="http://www.cs.wustl.edu/~schmidt/ACE-members.html">ACE
 development team</A> is creating a set of tutorials to help ACE
-newcomers learn how to use the framework effectively.  The following
-links provide further information on this topic. <P>
+newcomers learn how to use the framework effectively.  The original
+audience for these tutorials was the <A
+HREF="http://www.lads.com">Automated Design Systems</A> (ADS) IPC
+team, lead by <A HREF="mailto:jcej@lads.com">James Johnson</A>.  Since
+then, the scope has been changed to include anyone who wants to learn
+about the ACE framework. Hopefully, even experienced ACE programmers
+will find something new here. With a framework as encompassing as ACE,
+it is easy to become an expert in one area and know little or nothing
+about others. <P>
+
+The following links provide further information on this topic. <P>
 
 <TABLE cellpadding=10 cellspacing=0 border=0>
 <TD>
 <DL>
  <DT> <img alt="o" src="http://www.cs.wustl.edu/~schmidt/gifs/misc/redball.gif"> <A
- HREF="http://www.cs.wustl.edu/~schmidt/ACE_wrappers/docs/tutorials/index.html">Tutorials</A>
+ HREF="http://www.cs.wustl.edu/~schmidt/ACE-overview.html">Overview of ACE</A>
+
+ <DT> <img alt="o" src="http://www.cs.wustl.edu/~schmidt/gifs/misc/redball.gif"> <A
+ HREF="http://www.cs.wustl.edu/~schmidt/ACE_wrappers/docs/tutorials/index.html">Introductory Tutorials</A>
 
  <DT> <img alt="o" src="http://www.cs.wustl.edu/~schmidt/gifs/misc/redball.gif"> <A
  HREF="http://www.cs.wustl.edu/~schmidt/ACE_wrappers/docs/tutorials/new-tutorials.html">Developing New Tutorials</A>
@@ -24,7 +36,6 @@ links provide further information on this topic. <P>
 </TD>
 </TABLE>
 
-
 <HR><P>
 Back to the <A
 HREF="http://www.cs.wustl.edu/~schmidt/ACE-documentation.html">ACE
diff --git a/docs/tutorials/index.html b/docs/tutorials/index.html
index d0e136d5348..c497cb1704d 100644
--- a/docs/tutorials/index.html
+++ b/docs/tutorials/index.html
@@ -11,45 +11,8 @@
 <H3>
 ACE Tutorials</H3>
 
-The original audience for these tutorials was the <A
-HREF="http://www.lads.com">Automated Design Systems</A> (ADS) IPC
-team, lead by <A HREF="mailto:jcej@lads.com">James Johnson</A>. Since
-then, the scope has been changed to include anyone who wants to learn
-about the ACE framework. Hopefully, even experienced ACE programmers
-will find something new here. With a framework as encompassing as ACE,
-it is easy to become an expert in one area and know little or nothing
-about others.
-
-<P> <HR WIDTH="100%"> <H3> What is ACE?</H3> The <A
-HREF="http://www.cs.wustl.edu/~schmidt/ACE.html">ACE</A> framework was
-developed mostly by <A HREF="http://www.cs.wustl.edu/~schmidt">Douglas
-C. Schmidt's</A> team at Washington University. The framework attempts
-to abstract the details of many things across many operating
-systems. Some of the things abstracted include: network programming,
-multi-threading, shared memory and resource locking. 
-<!--#include virtual="/~schmidt/ACE-versions-i.html" -->
-
-<HR WIDTH="50%" align=left>
-<H3>
-Why Use ACE?</H3>
-A key reason to use ACE is simple: <I>write a multi-threaded networked
-application on one platform and quickly be able to use it on another</I>.
-This is important for many projects because it is necessary for applications
-to communicate with one another. For instance, many applications will exist
-on both UNIX and Win32 platforms within a local area network. <P>
-
-<HR WIDTH="50%" align=left>
-<H3>
-What about TAO?</H3>
-In the early stages, these tutorials won't address The ACE ORB (<A HREF="http://www.cs.wustl.edu/~schmidt">TAO</A>).
-However, if you want to request a tutorial on some aspect of TAO or even
-create one yourself, I'll be glad to integrate those into these tutorials.
-It's rare when folks want to write documentation, so nothing will be refused!
-
-<P>
-<HR WIDTH="100%">
-<H3>
-The Tutorials</H3>
+The following tutorials are designed to help get you started with
+ACE. <P>
 
 <P><HR WIDTH="50%" align=left><P>
 <H4>
diff --git a/docs/tutorials/new-tutorials.html b/docs/tutorials/new-tutorials.html
index 29130c37990..a886f6f0094 100644
--- a/docs/tutorials/new-tutorials.html
+++ b/docs/tutorials/new-tutorials.html
@@ -6,9 +6,9 @@
 
 Here are some general guidelines for creating new ACE tutorials: <P>
 
-<UL>
-<LI> Choose a topic that you know very well or are just learning.
-<P>
+<hr width=50% align=left>
+<H4>Choose a Topic You Know Very Well (or are just learning)</h4>
+
   This isn't really a conflict...
 <P>
   If you know a topic very well, you're likely to know what is most
@@ -16,7 +16,8 @@ Here are some general guidelines for creating new ACE tutorials: <P>
   just learning a topic, then you know what questions you have that
   must be answered before you can continue.
 <P>
-<LI> Keep it simple.
+<hr width=50% align=left>
+<H4> Keep It Simple</H4>
 <P>
   Don't try to use a lot of really cool ACE features along the way.  Stick
   to the basic stuff and show that.  Try to use a minimum of ACE objects
@@ -31,7 +32,8 @@ Here are some general guidelines for creating new ACE tutorials: <P>
   understand even if it isn't directly relevant to what you're trying
   to teach.
 <P>
-<LI> Document the heck out of it!
+<hr width=50% align=left>
+<h4>Document the Heck Out of It!</H4>
 <P>
   There's no such thing as too much documentation.  Don't worry about
   repeating yourself along the way.  Assume that the reader knows nothing
@@ -43,7 +45,8 @@ Here are some general guidelines for creating new ACE tutorials: <P>
   something.  Alternately, create both a well-documented version and a
   sparsely-documented version.  Then folks can choose between 'em.
 <P>
-<LI> Over-teach it.
+<hr width=50% align=left>
+<h4>Over-teach It</H4>
 <P>
   If there's a tutorial created for a topic that you feel strong in,
   create another one anyway.  Everybody tends to code a little differently.
@@ -51,18 +54,25 @@ Here are some general guidelines for creating new ACE tutorials: <P>
   than an existing tutorial.  You won't hurt anybody's feelings if
   you present the same material in a different way.
 <P>
-<LI> Steal existing code.
+<hr width=50% align=left>
+<h4>Leverage Existing Code</H4>
 <P>
   The ultimate form of code reuse :-)  Seriously...  grab one or more
   of the existing ACE tests or examples.  Then strip it down to the
   bare bones & add heaps of comments.  I don't think the software-police
   will be coming after anyone for that!
-</UL>
-<P>
-If this thing takes off, I'll start to organize the tutorials into
-groups.  For now, lets concentrate on quantity & quality.  Organization
-can come later...
-<P>
+
+<P> If this thing takes off, I'll start to organize the tutorials into
+groups.  For now, lets concentrate on quantity & quality.
+Organization can come later...  <P>
+
+<HR><P> <H3> What about TAO?</H3> In the early stages, these tutorials
+won't address The ACE ORB (<A
+HREF="http://www.cs.wustl.edu/~schmidt">TAO</A>).  However, if you
+want to request a tutorial on some aspect of TAO or even create one
+yourself, I'll be glad to integrate those into these tutorials.  It's
+rare when folks want to write documentation, so nothing will be
+refused!<P>
 
 <HR><P>
 Back to the <A