By Rafael H. Schloming and Pete Su
Writing OpenACS Application Pages
By Rafael H. Schloming and Pete Su
OpenACS docs are written by the named authors, and may be edited
by OpenACS documentation staff.
@@ -254,15 +254,15 @@
visible to that user. The end result is a site where users can come
and write notes to themselves.
-This is a good example of the leverage available in the OpenACS 5.7.0
+This is a good example of the leverage available in the OpenACS 5.9.0
system. The code that we have written for Notes is not at all more
complex than a similar application without access control or site map
awareness. By adding a small amount of code, we have taken a small,
simple, and special purpose application to something that has the
potential to be a very useful, general-purpose tool, complete with
multi-user features, access control, and centralized administration.
-In OpenACS 5.7.0, application pages and scripts can be aware of the package
+In OpenACS 5.9.0, application pages and scripts can be aware of the package
instance, or subsite in which they are executing. This is a powerful
general purpose mechanism that can be used to structure web services
in very flexible ways.
@@ -274,4 +274,4 @@
We also saw how to use the templating system's forms API in a simple
way, to create forms based pages with minimal duplication of code.
-
($Id$)