OpenACS Packages

By Pete Su and Bryan Quinn

+OpenACS Packages

Prev	Chapter 11. Development Reference	Next

OpenACS Packages

By Pete Su and Bryan Quinn

OpenACS docs are written by the named authors, and may be edited by OpenACS documentation staff.

Overview

@@ -13,7 +13,7 @@

Server file layout

Here is how an OpenACS 5 server is laid out starting from the Server root (ROOT): -

Figure 11.1. Server file layout diagram

+    
Figure 11.1. Server file layout diagram
 ROOT/
     bin/
         Various executables and scripts for server maintanence.
@@ -33,7 +33,7 @@
     www/
         Pages not in packages (static content, customized pages)

What a Package Looks Like

Each package encapsulates all of its data model, library code, - logic, adminstration pages and user pages in a single part of + logic, administration pages and user pages in a single part of the file tree. This means developers can track down everything that is related to a particular package without hunting all over the file system. Encapsulating @@ -51,7 +51,7 @@ To illustrate the general structure of a package, let's see what the package for the "notes" application should look like. -

Figure 11.2. Package file layout diagram

+    
Figure 11.2. Package file layout diagram
 ROOT/
   +-- packages/    APM Root
         |
@@ -124,7 +124,7 @@
       directories.  This makes it suitable for storing icons, css
       files, javascript, and other static content which can be treated
       this way.
-    
Table 11.1. Package files
File Type Its Use Naming Convention
Package Specification File The package specification file is an XML file generated and
+    
Table 11.1. Package files
File Type Its Use Naming Convention
Package Specification File The package specification file is an XML file generated and
           maintained by the OpenACS Package Manager (APM).  It specifies
           information about the package including its parameters and its
           files. notes.info
Data Model Creation Script 
@@ -149,9 +149,9 @@
           files and then have the scripts source the other data model
           files. In Oracle this can be done by including 
           @@ filename in the creation or drop
-          scripts. See the 
+          scripts. See the 
         Oracle FAQ for examples. In
-          PostgreSQL the same is acomplished by including \i filename.
+          PostgreSQL the same is accomplished by including \i filename.
         
           sql/<database>/*.sql
         
Data Model Upgrade Scripts 
@@ -427,4 +427,4 @@
     

       Writes out package distribution files for other people to download and
       install. We'll cover this later.
-    
Additional Reading
Package Manager Design
Package Manager Requirements
package development tutorial
($Id$)
Prev Home  Next
Chapter 11. Development Reference Up  OpenACS Data Models and the Object System
docs@openacs.org
View comments on this page at openacs.org
+    
Additional Reading
Package Manager Design
Package Manager Requirements
package development tutorial
($Id$)
Prev Home  Next
Chapter 11. Development Reference Up  OpenACS Data Models and the Object System
docs@openacs.org