by Joel Aufrecht
OpenACS docs are written by the named authors, and may be edited
by OpenACS documentation staff.
-
To start developing new code in OpenACS, we build a new
+
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; a package which provides
@@ -21,11 +21,11 @@
In this tutorial, we will make an application package for
displaying a list of text notes.
-
You will need:
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.0.1d1 distribution.
-
Use the APM to initialize a new package
We use the ACS Package Manager (APM) to add, remove, and
+standard OpenACS 5.1.0d1 distribution.
+
Use the APM to initialize a new package
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 package key. To start developing a new
@@ -54,7 +54,7 @@
This creates a package rooted at
/var/lib/aolserver/service0/packages/myfirstpackage.
This is the "home directory" of our new package, and all
- files in the package will be within this directory.
Mount the package in the site map
In order to see your work in progress, you must create a
map between the URL space of incoming requests and the package.
You do this by mounting the package in the Site Map. This
creates a link between the incoming URL and an
@@ -66,4 +66,4 @@
in this tutorial.
By mounting the package, we've caused all requests to
http://yourserver.test:8000/my-first-package
- to be satisfied from the files at /var/lib/aolserver/service0/packages/myfirstpackage/www.