Index: openacs-4/packages/acs-core-docs/www/apm-requirements.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/apm-requirements.html,v diff -u -r1.29 -r1.30 --- openacs-4/packages/acs-core-docs/www/apm-requirements.html 7 Jun 2008 20:28:49 -0000 1.29 +++ openacs-4/packages/acs-core-docs/www/apm-requirements.html 29 Dec 2008 22:21:04 -0000 1.30 @@ -4,7 +4,7 @@ by OpenACS documentation staff.
The following is a requirements document for the OpenACS Package Manager (APM), version 4.0 (APM4). APM4 offers a superset of APM v3.3 functionality -with the following specific enhancements:
A public procedural API. (v 3.3 only has web-based UI)
Support for dependency checking.
Support for compound packages (to support installation chaining).
Support for on-line parameter setting.
Support for sub-site level configuration (requires revised ad_parameter +with the following specific enhancements:
A public procedural API. (v 3.3 only has web-based UI)
Support for dependency checking.
Support for compound packages (to support installation chaining).
Support for on-line parameter setting.
Support for sub-site level configuration (requires revised parameter and /admin pages at sub-site level; deprecation of site-wide parameter file).
To differentiate these new requirements from the requirements of version 3.3, all requirements new in v4 are prefaced with the number @@ -36,7 +36,7 @@
Web-based tools for package development:
Creating new packages locally
Releasing new versions of locally-created packages
Uploading packages to a global package repository on the web
Use of these tools should be safe, i.e. installing or removing a package should never break an OpenACS installation
Web-based tools for package configuration:
The ability to change package parameter values on-line through a simple -web interface.
A new ad_parameter which does not require a monolithic site-wide +web interface.
A new parameter::get which does not require a monolithic site-wide parameter's file or server restarts for changes to take effect.
The ability to manage multiple package instances at the sub-site level.
The APM is intended for the following classes of users, which may or may not Index: openacs-4/packages/acs-core-docs/www/subsites-requirements.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/subsites-requirements.html,v diff -u -r1.28 -r1.29 --- openacs-4/packages/acs-core-docs/www/subsites-requirements.html 7 Jun 2008 20:28:51 -0000 1.28 +++ openacs-4/packages/acs-core-docs/www/subsites-requirements.html 29 Dec 2008 22:21:04 -0000 1.29 @@ -29,7 +29,7 @@ subcommunities.
Joe Programmer is working on the forum package and wants to make it subsite-aware. Using [ad_conn package_id], Joe adds code that only displays forum messages associated with the current package instance. Joe is happy to -realize that ad_parameter is already smart enough to return configuration +realize that parameter::get is already smart enough to return configuration parameters for the current package instance, and so he has to do no extra work to tailor configuration parameters to the current subsite.
Jane Admin maintains www.company.com. She learns of Joe's work and
would like to set up individual forums for the Boston and Austin offices of
Index: openacs-4/packages/acs-core-docs/www/xml/kernel/apm-requirements.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/apm-requirements.xml,v
diff -u -r1.8 -r1.9
--- openacs-4/packages/acs-core-docs/www/xml/kernel/apm-requirements.xml 17 Jul 2006 05:38:38 -0000 1.8
+++ openacs-4/packages/acs-core-docs/www/xml/kernel/apm-requirements.xml 29 Dec 2008 22:21:04 -0000 1.9
@@ -28,7 +28,7 @@