[hoc-cvs] [hoc] r403 committed - minor documentation corrections/updates

[<cod...@go...>]

Revision: 403
Author: wol...@gm...
Date: Mon Aug 17 10:26:56 2009
Log: minor documentation corrections/updates

http://code.google.com/p/hoc/source/detail?r=403

Modified:
  /trunk/hoc/docs/Appendices.pod
  /trunk/hoc/docs/Tools.pod

=======================================
--- /trunk/hoc/docs/Appendices.pod	Thu Mar 31 19:26:57 2005
+++ /trunk/hoc/docs/Appendices.pod	Mon Aug 17 10:26:56 2009
@@ -2,22 +2,9 @@

  =head2 Building HOC

-HOC is distributed as a standard UNIX tarball (F<.tar.bz2> file), and
-uses GNU I<autoconf> for its build system.  Building HOC should
-be a simple matter of the standard autoconf build mantra:
-
-  ./configure
-  make
-  make install
-
  See the F<README.txt> file in the HOC distribution for the most
  up-to-date build information.

-Building HOC from a CVS repository is only slightly more
-involved: see the F<BUILDING.CVS> file in your checked out CVS
-directory (which is not included in proper release tarball) for
-more information.
-
  =head2 Template Haskell in a Nutshell

  I<Template Haskell is an extension to Haskell 98 that allows you
=======================================
--- /trunk/hoc/docs/Tools.pod	Wed May 19 09:18:28 2004
+++ /trunk/hoc/docs/Tools.pod	Mon Aug 17 10:26:56 2009
@@ -1,17 +1,13 @@
  =head1 Tools

-=head2 F<hocwrap>
-
-The F<hocwrap> tool takes an executable and "wraps" it in a Mac OS
-X F<.app> application bundle.  You'll need to tell hocwrap where the
-bundle's F<Contents/> directory using the C<-c> command-line parameter.
-F<hocwrap> can also run the resulting application bundle using GHCi in an
-interactive fashion: more documentation about this will be coming in the
-future, but for now, check out the I<Browser> and I<Editor> applications'
-F<Makefile>s in HOC's F<Samples/> directory, for an idea of how to use the
-GHCi interaction feature.
-
-See C<hocwrap --help> for the definitive reference on F<hocwrap>.
+=head2 F<hoc-wrap>
+
+The F<hoc-wrap> tool takes an executable and "wraps" it in a Mac OS
+X F<.app> application bundle. It expects to find a F<Contents/> folder
+that already contains all the necessary ingredients for the bundle,
+except for the executable itself, in the current directory.
+
+See C<hoc-wrap --help> for the definitive reference on F<hocwrap>.

  =for comment Modeline for vi(m)
  vi:sw=2 tw=65