From 0581c39b392d3f75f8aa888358837c057eddfc7d Mon Sep 17 00:00:00 2001
From: mdb <mdb@6335cc39-0255-0410-8fd6-9bcaacd3b74c>
Date: Mon, 2 Aug 2004 03:26:55 +0000
Subject: [PATCH] Added savedoc, updated README and library dependencies.

git-svn-id: https://samskivert.googlecode.com/svn/trunk@1471 6335cc39-0255-0410-8fd6-9bcaacd3b74c
---
 projects/viztool/README     | 28 ++--------------------------
 projects/viztool/build.xml  | 14 ++++++++++++--
 projects/viztool/lib/README |  5 +----
 3 files changed, 15 insertions(+), 32 deletions(-)

diff --git a/projects/viztool/README b/projects/viztool/README
index d8282750..99794f19 100644
--- a/projects/viztool/README
+++ b/projects/viztool/README
@@ -18,21 +18,6 @@ to Sunday, generate code, count my chickens and make toast on the side,
 but I couldn't find a free, simple tool for generating basic class
 diagrams.
 
-Thus, viztool aims to provide an extensible framework for generating
-visualizations of collections of classes. This initial release generates
-inheritance diagrams organized by package, with information on interfaces
-implemented and (non-anonymous) inner classes as well. It is somewhat
-modular, although not as thoroughly as I'd like because, like all
-projects, it was completed in haste and with an eagerness to see the final
-product that isn't entirely conducive to elaborate design. There are also
-various enhancements I'd like to make to the inheritance visualization.
-
-Excuses aside, the foundation is laid and adding other visualizations
-should be a reasonably straightforward process after having had a look at
-the existing code. So if you've got some handy visualization in mind, take
-a crack at it, or at least email me with the idea so that I can put it on
-a list and someone else might do it for you.
-
 Building viztool
 ----------------
 
@@ -111,16 +96,7 @@ available here:
 Contribution
 ------------
 
-Contributions are welcome. Control of the CVS repository is presently in
-the hands of mdb@samskivert.com, who should be emailed about submissions.
-Facilities for management of major contributions by external parties
-(ie. publicly accessible CVS server) will be provided if circumstances
-dictate.
-
-Contact Information
--------------------
-
-The person primarily responsible for viztool is Michael Bayne and can be
-contacted at <mdb@samskivert.com>.
+Contributions are welcome. Patches and suggestions can be sent to Michael
+Bayne <mdb@samskivert.com>.
 
 $Id: README,v 1.3 2001/12/03 08:34:05 mdb Exp $
diff --git a/projects/viztool/build.xml b/projects/viztool/build.xml
index 9ac67a7d..b2bfd76c 100644
--- a/projects/viztool/build.xml
+++ b/projects/viztool/build.xml
@@ -14,6 +14,7 @@
   <property name="deploy.dir"  value="dist"/>
   <property name="dist.jar"    value="${app.name}.jar"/>
   <property name="javadoc.dir" value="${deploy.dir}/docs"/>
+  <property name="savedoc.dir" value="docs"/>
 
   <!-- declare our classpath business -->
   <path id="base.classpath">
@@ -67,11 +68,20 @@
              destdir="${javadoc.dir}"
              additionalparam="-breakiterator">
       <classpath refid="classpath"/>
-      <link href="http://www.waywardgeeks.org/code/samskivert/javadoc"/>
-      <link href="http://java.sun.com/j2se/1.3/docs/api/"/>
+      <link href="http://samskivert.com/code/samskivert/samskivert/dist/api"/>
+      <link href="http://java.sun.com/j2se/1.4/docs/api/"/>
     </javadoc>
   </target>
 
+  <!-- builds the javadocs and stuffs them in a directory where they won't
+       be blown away when we do "clean" next time -->
+  <target name="savedoc" depends="javadoc">
+    <delete dir="${savedoc.dir}/api"/>
+    <copy todir="${savedoc.dir}/api">
+      <fileset dir="${javadoc.dir}" includes="**/*"/>
+    </copy>
+  </target>
+
   <!-- a target for rebuilding everything -->
   <target name="all" depends="clean,prepare,compile,javadoc,dist"/>
 
diff --git a/projects/viztool/lib/README b/projects/viztool/lib/README
index e432975c..5784bd7f 100644
--- a/projects/viztool/lib/README
+++ b/projects/viztool/lib/README
@@ -6,10 +6,7 @@ files) to be placed here in the lib/ directory or in the shared library
 directory specified in the build.xml file (${java.libraries}).
 
 * samskivert library: 
-  http://www.waywardgeeks.org/code/samskivert/
-
-* Jakarta Regular Expression package: 
-  http://jakarta.apache.org/regexp/
+  http://samskivert.com/code/samskivert/
 
 Once the jar files are in place (regardless of what they are named), the
 build system will automatically include them in the compile-time