Using Templates in OpenACS
By Pete Su
OpenACS docs are written by the named authors, and may be edited
by OpenACS documentation staff.
-
The OpenACS Template System (ATS) is designed to allow developers to
cleanly separate application logic from display
logic. The intent is to have all of the logic related to
@@ -28,7 +28,7 @@
actually add notes to the database, how to provide a separate instance
of the Notes application to every user and how to design appropriate
access control policies for the system.
-
In order for the Notes application to be useful, we have to allow
users to enter data into the database. Typically, this takes two
pages: one that displays a form for data entry, and another page that
@@ -156,7 +156,7 @@
After putting all these files into
ROOT/packages/notes/www, you should be able to go to
/notes/ URL for your server and see the input form.
-
Templates separate application logic from display logic by requiring
the developer to write pages in two stages, one file for database
queries and application logic, and another for display. In OpenACS, the
@@ -167,4 +167,4 @@
inserting properties into the text of the page. Later on we'll get
into templates more deeply, and show how to use database queries as
data sources.
-