| Prev | Chapter�8.�Development Reference | Next |
|---|
By Pete Su and Bryan Quinn
+@@ -15,7 +15,6 @@ 3.2.x and earlier, a typical server might have a file system behind it that looked something like this:
-
ROOT/
bin/
parameters/
@@ -45,8 +44,7 @@
core and application data models here
... and so on for all modules ...
-
- +
In previous versions of OpenACS, you wrote a new application like this:
Put all Tcl library procedures under server-root/tcl.
Put all User viewable content under @@ -58,9 +56,8 @@ the pieces of each module are strewn all over the tree in at least 3 or 4 different areas.
- Here is how an OpenACS 5.0.0b1 server is laid out: + Here is how an OpenACS 5.0.0b4 server is laid out:
-
ROOT/
bin/
packages/
@@ -79,6 +76,10 @@
acs-workflow/
forums/
forums.info
+ catalog/
+ i18n message catalogs
+ lib/
+ includable page fragments (.tcl/.adp pairs)
sql/
oracle/
oracle data model
@@ -87,11 +88,11 @@
tcl/
tcl library code
www/
+ user visible pages
admin/
- administration pages
- other pages
+ administration pages
doc/
- documentation
+ documentation
message-catalog/
news/
notification/
@@ -100,7 +101,7 @@
bootstrap code
www/
misc pages
- +
Note that a major reorganization has happened here. The diagram only expands the structure of the forums/ package directory, but all the others are basically the same. Each package encapsulates @@ -122,7 +123,7 @@ sends to our server to the right page in the appropriate package. While we're at it, this tool should also automate package installation, dependency checking, upgrades, and package - removal. In OpenACS 5.0.0b1, this tool is called the APM. + removal. In OpenACS 5.0.0b4, this tool is called the APM.
The APM is used to create, maintain, and install packages. It takes care of copying all of the files and registering the package in the @@ -144,7 +145,7 @@
The following sections will show you how to make a package for the Notes application. In addition, they will discuss some new site - management features in OpenACS 5.0.0b1 that take advantage of the APM's package + management features in OpenACS 5.0.0b4 that take advantage of the APM's package instance model. The two most important of these are subsites, and the site map tool, which can be used to map applications to one or more arbitrary URLs in a running site. @@ -395,7 +396,7 @@ this point, you should add your package files to your CVS repository. I'll assume that you have set up your development repository according to the standards described in - this appendix. If so, then you just do this: + this appendix. If so, then you just do this:
% cd ROOT/packages
@@ -432,7 +433,7 @@
map content that lived outside the page root into the site, and it was
also hard to map mulitiple URLs to the same place in the file system.
- In OpenACS 5.0.0b1, administrators can define an arbitrary mapping between the
+ In OpenACS 5.0.0b4, administrators can define an arbitrary mapping between the
URLs the user types and the actual file in the file system that is
served. This mapping is called the site map and entries in the
site map are called site nodes. Each site node maps a URL to an
@@ -447,7 +448,7 @@
of many indedendent applications that actually run on a single shared
code base. The request-processor document shows
you how OpenACS figures out which instance of your application was
- requested by the user at any given time. The page development tutorial shows you how to use this
+ requested by the user at any given time. The page development tutorial shows you how to use this
information in your user interface.
In order to make the new notes application visible to
@@ -474,7 +475,7 @@
yet written Notes application at various places in the site. In a
later document, we'll see how to write your application so that the
code can detect from what URL it was invoked. This is the key
- to supporting subsites.
+ to supporting subsites.
The APM performs the following tasks in an OpenACS site:
@@ -490,4 +491,4 @@
Writes out package distribution files for other people to download and install. We'll cover this later. -