Index: openacs-4/packages/acs-core-docs/www/apm-design.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/apm-design.html,v diff -u -r1.22 -r1.23 --- openacs-4/packages/acs-core-docs/www/apm-design.html 19 Nov 2003 15:44:49 -0000 1.22 +++ openacs-4/packages/acs-core-docs/www/apm-design.html 11 Dec 2003 23:08:45 -0000 1.23 @@ -1,7 +1,7 @@ -OpenACS 5.0.0b1 Package Manager Design

OpenACS 5.0.0b1 Package Manager Design

By Bryan Quinn

+Package Manager Design

Package Manager Design

By Bryan Quinn

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

Essentials

  • OpenACS Administrator directory

  • OpenACS 5.0.0b1 Package Manager Requirements

  • Packages

  • ER diagram

  • Tcl API

    Essentials

    Consistent use of the APM format and tools will go a long way toward solving the maintainability problems listed above. Moreover, APM is the -substrate that will enable us to soon establish a central package repository, -where both ArsDigita and third-party developers will be able publish their -packages for other ACS users to download and install.

    For a simple illustration of the difference between ACS without APM +substrate that will enable us to establish a central package repository, +where developers will be able publish their +packages for other OpenACS users to download and install.

    For a simple illustration of the difference between ACS without APM (pre-3.3) and ACS with APM (3.3 and beyond), consider a hypothetical ACS installation that uses only two of the thirty-odd modules available circa ACS -3.2 (say, bboard and e-commerce):

    APM itself is part of a package, the OpenACS Kernel, an OpenACS +3.2 (say, bboard and e-commerce):

    APM itself is part of a package, the OpenACS Kernel, an OpenACS service that is the only mandatory component of an OpenACS installation.

    Competitive Analysis

    The OpenACS is a platform for web-based application software, and any software platform has the potential to develop problems like those described above. Fortunately, there are many precedents for systematic solutions, @@ -540,4 +540,4 @@ all of this functionality in one interface and it can be confusing from a usability perspective.

    Authors

    • System creator: Bryan Quinn, Jon Salz, Michael Yoon, Lars Pind, Todd Nightingale.

    • System owner: Bryan Quinn

    • Documentation author: Bryan Quinn, building from earlier versions by Jon -Salz, Michael Yoon, and Lars Pind.

    Revision History

    Document Revision #Action Taken, NotesWhen?By Whom?
    0.1Creation9/25/2000Bryan Quinn
    0.8Ready for QA9/29/2000Bryan Quinn
    0.9Edited for ACS 4 Beta release10/02/2000Kai Wu
    1.0Edited for OpenACS 5.0.0b1 Beta release03/02/2002Roberto Mello
View comments on this page at openacs.org
+Salz, Michael Yoon, and Lars Pind.

Revision History

Document Revision #Action Taken, NotesWhen?By Whom?
0.1Creation9/25/2000Bryan Quinn
0.8Ready for QA9/29/2000Bryan Quinn
0.9Edited for ACS 4 Beta release10/02/2000Kai Wu
1.0Edited for OpenACS 4.5 Beta release03/02/2002Roberto Mello
View comments on this page at openacs.org