Index: openacs-4/packages/acs-core-docs/www/tutorial-newpackage.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-newpackage.adp,v diff -u -r1.1.2.21 -r1.1.2.22 --- openacs-4/packages/acs-core-docs/www/tutorial-newpackage.adp 17 Jun 2017 10:28:29 -0000 1.1.2.21 +++ openacs-4/packages/acs-core-docs/www/tutorial-newpackage.adp 18 Jun 2017 09:08:35 -0000 1.1.2.22 @@ -18,7 +18,7 @@ The intended page map
To start developing new code in OpenACS, we build a new package. A package is a a discrete collection of web pages, Tcl code, and database tables and procedures. A package with user interface is called an application; @@ -36,14 +36,14 @@ displaying a list of text notes.
You will need:
A computer with a working installation of OpenACS. If you don't have this, see Chapter 2, Installation Overview .
Example files, which are included in the standard OpenACS 5.9.0 distribution.
Figure 9.1. Assumptions in this
+ Figure 9.1. Assumptions in this
section We use the ACS Package Manager (APM) to add, remove, and upgrade
packages. It handles package meta-data, such as lists of files that
belong in the package. Each package is uniquely identified by a
@@ -102,7 +102,7 @@
packages). In order to see your work in progress, you must create a map
between the URL space of incoming requests and the package
application instance. You do this by adding the application in the
@@ -121,7 +121,7 @@
to be satisfied from the files at The remainder of the tutorial walks you through each file one at
a time as you create the package. You can skip all this, and get a
working package, by doing the following:
/var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/myfirstpackage/www
.
cd /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/acs-core-docs/www/files/tutorial