Index: openacs-4/packages/acs-templating/www/doc/design.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/design.adp,v
diff -u -r1.9.2.1 -r1.9.2.2
--- openacs-4/packages/acs-templating/www/doc/design.adp 15 Aug 2019 10:13:07 -0000 1.9.2.1
+++ openacs-4/packages/acs-templating/www/doc/design.adp 15 Aug 2019 10:18:49 -0000 1.9.2.2
@@ -265,7 +265,7 @@
template
to never
or always
.
The former suppresses checking mtime and may improve performance on
a production server, where the content pages don't change. The
-latter is only inteded for testing.
This package doesn't need a data model.
It comes with its own database interfaces, one for using ns_ora,
Index: openacs-4/packages/acs-templating/www/doc/design.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/design.html,v
diff -u -r1.10.2.1 -r1.10.2.2
--- openacs-4/packages/acs-templating/www/doc/design.html 15 Aug 2019 10:13:07 -0000 1.10.2.1
+++ openacs-4/packages/acs-templating/www/doc/design.html 15 Aug 2019 10:18:49 -0000 1.10.2.2
@@ -416,7 +416,7 @@
template
to never
or
always
. The former suppresses checking mtime and
may improve performance on a production server, where the
- content pages don't change. The latter is only inteded for testing.
+ content pages don't change. The latter is only intended for testing.
This training module will teach largely by exercise and example, but you should also refer regularly to the ATS documents provided and more specific Index: openacs-4/packages/acs-templating/www/doc/exercise/ats-for-designers.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/exercise/ats-for-designers.html,v diff -u -r1.5 -r1.5.2.1 --- openacs-4/packages/acs-templating/www/doc/exercise/ats-for-designers.html 4 Jul 2018 10:16:05 -0000 1.5 +++ openacs-4/packages/acs-templating/www/doc/exercise/ats-for-designers.html 15 Aug 2019 10:18:49 -0000 1.5.2.1 @@ -33,7 +33,7 @@
First, perhaps an explanation of what the templating system does will help us understand how it works. An ATS template itself serves as a reusable, unchanging framework that delivers dynamic data. The advantage to this is something you probably already realize: you need only build -and edit a few pages to maintain a consistent presentation style while accommodating numerous permutaions of changing data. +and edit a few pages to maintain a consistent presentation style while accommodating numerous permutations of changing data.
This training module will teach largely by exercise and example, but you should also refer regularly to the ATS documents provided and more specific pointers will be given to help you out along the way. Index: openacs-4/packages/acs-templating/www/doc/guide/wizard-procs-doc.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/guide/wizard-procs-doc.adp,v diff -u -r1.6 -r1.6.2.1 --- openacs-4/packages/acs-templating/www/doc/guide/wizard-procs-doc.adp 21 May 2018 16:40:47 -0000 1.6 +++ openacs-4/packages/acs-templating/www/doc/guide/wizard-procs-doc.adp 15 Aug 2019 10:18:49 -0000 1.6.2.1 @@ -155,7 +155,7 @@ load_last_visited_step -key $yourkey" before "template::wizard get_current_step", after "get_current_step" call "template::wizard -save_last_visited_step -key $yourkey"
Also the wizard params name is present across the curent wizards +save_last_visited_step -key $yourkey"
Also the wizard params name is present across the current wizards being used, so the developer has to be aware not to use the same names with different purpose. For example on main wizard with have a param called "name" for the user name. And on on sub Index: openacs-4/packages/acs-templating/www/doc/guide/wizard-procs-doc.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/guide/wizard-procs-doc.html,v diff -u -r1.4 -r1.4.2.1 --- openacs-4/packages/acs-templating/www/doc/guide/wizard-procs-doc.html 21 May 2018 16:40:47 -0000 1.4 +++ openacs-4/packages/acs-templating/www/doc/guide/wizard-procs-doc.html 15 Aug 2019 10:18:49 -0000 1.4.2.1 @@ -183,7 +183,7 @@ after "get_current_step" call "template::wizard save_last_visited_step -key $yourkey"
-Also the wizard params name is present across the curent wizards being used, +
Also the wizard params name is present across the current wizards being used, so the developer has to be aware not to use the same names with different purpose. For example on main wizard with have a param called "name" for the user name. And on on sub wizard we have the param again called "name" Index: openacs-4/packages/acs-templating/www/doc/widgets/date.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/widgets/date.adp,v diff -u -r1.3 -r1.3.2.1 --- openacs-4/packages/acs-templating/www/doc/widgets/date.adp 7 Aug 2017 23:48:03 -0000 1.3 +++ openacs-4/packages/acs-templating/www/doc/widgets/date.adp 15 Aug 2019 10:18:49 -0000 1.3.2.1 @@ -71,7 +71,7 @@
short_month_name
Jan
days_in_month
29
short_year
days_in_month
29
Each of these applications requires a message store and each - defines its own high level organization for messages whithin that + defines its own high-level organization for messages within that store.