Index: openacs-4/packages/acs-templating/www/doc/guide/composite.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/guide/composite.adp,v diff -u -r1.3 -r1.4 --- openacs-4/packages/acs-templating/www/doc/guide/composite.adp 7 Aug 2017 23:48:03 -0000 1.3 +++ openacs-4/packages/acs-templating/www/doc/guide/composite.adp 27 Mar 2018 11:18:00 -0000 1.4 @@ -59,13 +59,13 @@

Any (sub)page can have 0 or 1 master and 0 or more included pages. Each page has its own separate scope for variables. Arguments can be passed to dependent pages as attributes to -<inlcude>, or as properties to +<include>, or as properties to <master>. The directed graph of pages will often be be acyclic, as in the example, but this is not required.

Evaluation Order

Sometimes it is of interest in which order the different parts are evaluated. The "code" always runs first, followed by -the template. The <inlcude> tag causes the +the template. The <include> tag causes the subpage to be evaluated at this point of the template, and the rest of the including template is evaluated after that's done. This is like a procedure call. In contrast, the @@ -151,4 +151,4 @@

It is an error to omit both parts; this is a special case intended to speed up debugging.

- \ No newline at end of file +