| Prev | Chapter 11. Development Reference | Next |
|---|
By Pete Su and Bryan Quinn
-======= -By Pete Su and Bryan Quinn
->>>>>>> 1.49 +Here is how an OpenACS 5 server is laid out starting from the Server root (ROOT): -<<<<<<< packages.html -
Figure 11.1. Server file layout diagram
-======= -Figure 10.1. Server file layout diagram
->>>>>>> 1.49 +Figure 11.1. Server file layout diagram
ROOT/ bin/ Various executables and scripts for server maintanence. @@ -59,13 +50,8 @@To illustrate the general structure of a package, let's see what the -<<<<<<< packages.html - package for the "notes" application should look like. -
Figure 11.2. Package file layout diagram
-======= package for the "notes" application should look like. -Figure 10.2. Package file layout diagram
->>>>>>> 1.49 +Figure 11.2. Package file layout diagram
ROOT/ +-- packages/ APM Root | @@ -138,11 +124,7 @@ directories. This makes it suitable for storing icons, css files, javascript, and other static content which can be treated this way. -<<<<<<< packages.html -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 10.1. Package files
File Type Its Use Naming Convention Package Specification File The package specification file is an XML file generated and ->>>>>>> 1.49 + 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.infoData Model Creation Script @@ -367,11 +349,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 -<<<<<<< packages.html - this appendix. If so, then you just do this: -======= this appendix. If so, then you just do this: ->>>>>>> 1.49 % cd ROOT/packages % cvs add notes % cd notes @@ -383,13 +361,8 @@ % cvs commit -m "add new package for notes"Now you can start developing the package. In addition to writing code, -<<<<<<< packages.html - you should also consider the tasks outlined in the package development tutorial. -
-======= you should also consider the tasks outlined in the package development tutorial.
->>>>>>> 1.49 At this point, you are probably excited to see your new package in action. But, we haven't added any user visible pages yet. By convention, user visible pages go in the @@ -416,11 +389,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 -<<<<<<< packages.html - 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 ->>>>>>> 1.49 information in your user interface.
In order to make the new
notesapplication visible to @@ -442,13 +411,8 @@ 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 -<<<<<<< packages.html - to supporting subsites. --======= to supporting subsites.
->>>>>>> 1.49 The APM performs the following tasks in an OpenACS site:
Manages creation, installation, and removal of packages from the @@ -463,8 +427,4 @@
Writes out package distribution files for other people to download and install. We'll cover this later. -<<<<<<< packages.html -
($Id$)View comments on this page at openacs.org -======= -($Id$)View comments on this page at openacs.org ->>>>>>> 1.49 +($Id$)View comments on this page at openacs.org