Writing OpenACS Application Pages

By Rafael H. Schloming and Pete Su

+ +Writing OpenACS Application Pages

Prev	Chapter�11.�Development Reference	Next

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.

Overview

@@ -86,11 +87,11 @@ if {[info exists note_id]} { permission::require_permission -object_id $note_id -privilege write - set context_bar [ad_context_bar "Edit Note"] + set context_bar [ad_context_bar "Edit Note"] } else { permission::require_permission -object_id $note_id -privilege create - set context_bar [ad_context_bar "New Note"] + set context_bar [ad_context_bar "New Note"] }

@@ -152,7 +153,7 @@ <hr> <center> -<formtemplate id="new_note"></formtemplate> +<formtemplate id="new_note"></formtemplate> </center>

@@ -233,7 +234,7 @@ } } - ad_returnredirect "." + ad_returnredirect "." }

@@ -253,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.2.0d1 +This is a good example of the leverage available in the OpenACS 5.2.3b1 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.

Summary

-In OpenACS 5.2.0d1, application pages and scripts can be aware of the package +In OpenACS 5.2.3b1, 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.