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.4.2.2 -r1.4.2.3 --- openacs-4/packages/acs-templating/www/doc/design.html 21 Apr 2017 16:50:30 -0000 1.4.2.2 +++ openacs-4/packages/acs-templating/www/doc/design.html 22 Apr 2017 18:30:26 -0000 1.4.2.3 @@ -185,7 +185,7 @@ distinguish it from the obsolescent templates or "Styles" by Philip Greenspun. An extended and improved version was named "Dynamic Publishing System". It wasn't part of the ACS yet, but - client projects like iluvCAMP used it successfuly. Newcomers + client projects like iluvCAMP used it successfully. Newcomers were consistently puzzled by the .data files, which specified the datasources in an apparently unfamiliar XML syntax. (The .form files specified elements in an @@ -324,7 +324,7 @@ -properties block indicates a set of data sources that will be made available to the template.
  • - The rest of the tcl script executes, defining these data + The rest of the Tcl script executes, defining these data sources. It may change the name of the page being served by calling template::set_file directly or through the wrapper ad_return_template. @@ -392,12 +392,12 @@

    Caching and Template Compilation

    - To improve performance, adp pages are compiled into a tcl proc, + To improve performance, adp pages are compiled into a Tcl proc, and thus cached for future use. Tcl pages are also cached in a proc; this saves the trouble of reading and parsing the file the next time. The template system remembers the modification times of the adp and - tcl sources, and re-processes any requested file if the cached + Tcl sources, and re-processes any requested file if the cached version is no longer current. Consequently, this cacheing is transparent in normal use.

    Index: openacs-4/packages/acs-templating/www/doc/developer-guide.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/developer-guide.html,v diff -u -r1.4 -r1.4.2.1 --- openacs-4/packages/acs-templating/www/doc/developer-guide.html 16 Jun 2015 08:53:38 -0000 1.4 +++ openacs-4/packages/acs-templating/www/doc/developer-guide.html 22 Apr 2017 18:30:26 -0000 1.4.2.1 @@ -15,13 +15,13 @@ Start a Tcl page as usual with ad_page_contract. Be sure to pass a -properties block; this signals the - use of templating. The tcl page should fill the data sources you + use of templating. The Tcl page should fill the data sources you promised in the contract, and not write to the connection. At the - end of your tcl page, call ad_return_template. The + end of your Tcl page, call ad_return_template. The template system will look for an adp page with the file name stub - you indicate (defaulting to the same stub as the tcl page), + you indicate (defaulting to the same stub as the Tcl page), process that, and deliver it to the client. The adp page can use - the datasources defined in the tcl page. + the datasources defined in the Tcl page.

    Guide

      @@ -110,7 +110,7 @@ template::set_file, to change the name of the page being served currently. If it starts with a "/", it is taken to be a path relative to the server root; otherwise it is - a filename relative to the directory of the tcl script. + a filename relative to the directory of the Tcl script.

      ad_page_contract
      Index: openacs-4/packages/acs-templating/www/doc/index.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/index.html,v diff -u -r1.6.2.4 -r1.6.2.5 --- openacs-4/packages/acs-templating/www/doc/index.html 1 Dec 2016 19:24:14 -0000 1.6.2.4 +++ openacs-4/packages/acs-templating/www/doc/index.html 22 Apr 2017 18:30:26 -0000 1.6.2.5 @@ -57,7 +57,7 @@ Migration - Bringing legacy tcl pages to use the template system. + Bringing legacy Tcl pages to use the template system. Demonstration Index: openacs-4/packages/acs-templating/www/doc/migration.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/migration.html,v diff -u -r1.3.2.1 -r1.3.2.2 --- openacs-4/packages/acs-templating/www/doc/migration.html 22 Jun 2016 07:48:43 -0000 1.3.2.1 +++ openacs-4/packages/acs-templating/www/doc/migration.html 22 Apr 2017 18:30:26 -0000 1.3.2.2 @@ -12,7 +12,7 @@

      In a Nutshell

      - When templatizing a legacy tcl page, your task is to + When templatizing a legacy Tcl page, your task is to separate code and graphical presentation. The latter goes into an ADP file; it contains essentially HTML, augmented by a few special tags and the @variable@ construct. @@ -36,7 +36,7 @@

      At the end of the Tcl script, you should call ad_return_template. The template runs after the - tcl script, and can use these data sources. + Tcl script, and can use these data sources.

      Make sure that the fancy adp parser is enabled in your AOL ini @@ -54,13 +54,13 @@ wait till the headers are written or the page is completed; they may act differently than you expect.

    1. - If you can, put code in the tcl file, not between <% + If you can, put code in the Tcl file, not between <% %> in the adp page.
    2. - Put HTML in the adp page, not int the tcl program. Put + Put HTML in the adp page, not int the Tcl program. Put reusable HTML fragments in a separate adp file (think of it as a widget) that will be <include>d from - several pages. Prefer this to writing a tcl proc that returns + several pages. Prefer this to writing a Tcl proc that returns HTML.
    3. Remember to remove backslashes where you had to escape special @@ -92,7 +92,7 @@

      - + @@ -251,7 +251,7 @@
      old tcl codeold Tcl code new
      - + @@ -420,12 +420,12 @@ own multirow variable. In the excert below, taken from /pvt/alerts.tcl and /pvt/alerts.adp, the foreach logic made it hard to use the db_multirow because it needed a combination of the - output from sql and also the output of tcl procedures using that + output from sql and also the output of Tcl procedures using that value.
      old tcl codeold Tcl code new
      - + Index: openacs-4/packages/acs-templating/www/doc/noquote.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/noquote.html,v diff -u -r1.1.24.3 -r1.1.24.4 --- openacs-4/packages/acs-templating/www/doc/noquote.html 21 Apr 2017 16:50:30 -0000 1.1.24.3 +++ openacs-4/packages/acs-templating/www/doc/noquote.html 22 Apr 2017 18:30:26 -0000 1.1.24.4 @@ -198,7 +198,7 @@ broken page from time to time, typically by spotting the obviously visible HTML markup. Such a page would get fixed it in a matter of seconds by appending ;noquote to the name of the offending variable. -

      We launched successfuly within schedule. +

      We launched successfully within schedule.

      Porting the quoting changes to the ACS.

      After some discussion, it was decided that these changes will be Index: openacs-4/packages/acs-templating/www/doc/TclDocs/doc.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/TclDocs/doc.html,v diff -u -r1.2.30.1 -r1.2.30.2 --- openacs-4/packages/acs-templating/www/doc/TclDocs/doc.html 22 Jun 2016 07:48:44 -0000 1.2.30.1 +++ openacs-4/packages/acs-templating/www/doc/TclDocs/doc.html 22 Apr 2017 18:30:26 -0000 1.2.30.2 @@ -40,7 +40,7 @@

      old tcl codeold Tcl code new
      -called by parse_file, this procedure is given the body of text between two namespace markers in a tcl library file and parses out procedure source and comments +called by parse_file, this procedure is given the body of text between two namespace markers in a Tcl library file and parses out procedure source and comments
      @@ -151,7 +151,7 @@
      -takes the absolute path of the tcl library directory and parses through it +takes the absolute path of the Tcl library directory and parses through it
      Index: openacs-4/packages/acs-templating/www/doc/TclDocs/util.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/TclDocs/util.html,v diff -u -r1.2.30.1 -r1.2.30.2 --- openacs-4/packages/acs-templating/www/doc/TclDocs/util.html 22 Jun 2016 07:48:44 -0000 1.2.30.1 +++ openacs-4/packages/acs-templating/www/doc/TclDocs/util.html 22 Apr 2017 18:30:26 -0000 1.2.30.2 @@ -237,7 +237,7 @@
      -uses ns_library to find the server root, may not always be accurate because it essentially asks for the tcl library path and strips off the last /tcl directory +uses ns_library to find the server root, may not always be accurate because it essentially asks for the Tcl library path and strips off the last /tcl directory
      Index: openacs-4/packages/acs-templating/www/doc/demo/index.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/demo/index.html,v diff -u -r1.13.2.3 -r1.13.2.4 --- openacs-4/packages/acs-templating/www/doc/demo/index.html 1 Dec 2016 20:43:45 -0000 1.13.2.3 +++ openacs-4/packages/acs-templating/www/doc/demo/index.html 22 Apr 2017 18:30:26 -0000 1.13.2.4 @@ -10,7 +10,7 @@ As the links reveal, the "Data" files have the extension .tcl and the "Template" files have .adp. If you want to see a little behind the scenes, - you can look at the tcl code into which we compile the template. + you can look at the Tcl code into which we compile the template. The last column will deliver the resulting page to your browser.

      Mechanisms underlaid in red are known to not work. Index: openacs-4/packages/acs-templating/www/doc/guide/composite.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/guide/composite.html,v diff -u -r1.3.2.2 -r1.3.2.3 --- openacs-4/packages/acs-templating/www/doc/guide/composite.html 1 Dec 2016 20:43:45 -0000 1.3.2.2 +++ openacs-4/packages/acs-templating/www/doc/guide/composite.html 22 Apr 2017 18:30:26 -0000 1.3.2.3 @@ -213,7 +213,7 @@

      - Here we assume the ACS/Tcl situation, where the "code" is a tcl + Here we assume the ACS/Tcl situation, where the "code" is a Tcl script in a .tcl file. The template is a .adp file.

      Index: openacs-4/packages/acs-templating/www/doc/guide/form-widgets.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/guide/form-widgets.html,v diff -u -r1.3 -r1.3.10.1 --- openacs-4/packages/acs-templating/www/doc/guide/form-widgets.html 29 Jul 2008 19:22:24 -0000 1.3 +++ openacs-4/packages/acs-templating/www/doc/guide/form-widgets.html 22 Apr 2017 18:30:26 -0000 1.3.10.1 @@ -9,17 +9,17 @@ User Guide

      - Form widgets are implemented as tcl procs that output the - html to generate the form element. The tcl proc must be in + Form widgets are implemented as Tcl procs that output the + html to generate the form element. The Tcl proc must be in the template::widget namespace. So the proc for the search widget is called template::widget::search. The code that generates the built in widgets is in packages/acs-templating/tcl/widget-procs.tcl.

      If the data from the form widget needs to be formatted or - processed a tcl proc is created in the + processed a Tcl proc is created in the template::data::transform namespace. For example, templatete::data::transform::search. This takes the input from the user and processes it - to be returned to the tcl code handling the form. + to be returned to the Tcl code handling the form.

      Index: openacs-4/packages/acs-templating/www/doc/guide/tcl.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/guide/tcl.html,v diff -u -r1.2.2.1 -r1.2.2.2 --- openacs-4/packages/acs-templating/www/doc/guide/tcl.html 1 Dec 2016 20:43:45 -0000 1.2.2.1 +++ openacs-4/packages/acs-templating/www/doc/guide/tcl.html 22 Apr 2017 18:30:26 -0000 1.2.2.2 @@ -17,7 +17,7 @@

      Generally, avoid putting escaped Tcl code in adp files, or - generating HTML fragments in tcl procedures. It subverts the + generating HTML fragments in Tcl procedures. It subverts the separation of code and layout, one of the benefits of templating. Embedded Tcl makes templates non-portable to ACS/Java.

      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.1 -r1.1.24.1 --- openacs-4/packages/acs-templating/www/doc/guide/wizard-procs-doc.html 30 Sep 2003 12:04:22 -0000 1.1 +++ openacs-4/packages/acs-templating/www/doc/guide/wizard-procs-doc.html 22 Apr 2017 18:30:26 -0000 1.1.24.1 @@ -23,7 +23,7 @@ same as your current wizard file. Has no effect for subwizards.
    4. name - use to distinguish between the different wizards, since you can have 1 or more subwizard. name must be no spaces, alpanumeric similar - to normal tcl variable naming convention
      5. + to normal Tcl variable naming convention
    5. params - are used to keep values that you would like to pass on to the other steps
    6. steps - are use to define what includes to use for each step of the @@ -48,7 +48,7 @@
      7. -
    7. Create the individual steps, these are just normal tcl and/or adp files. +
    8. Create the individual steps, these are just normal Tcl and/or adp files. So make a step1.tcl, step1.adp, step2.tcl, step2.adp, step3.tcl and step3.adp. Normally this files are self submitting forms
      9. @@ -134,8 +134,8 @@ get the current value of the param which was set by "template::wizard set_param", while ad_page_contract will not pick that up since it will get what is the request http var value. This is because "template::wizard get_param" gets the value - from the tcl var while ad_page_contract gets the value from the http var. - So while processing in tcl that value may change. + from the Tcl var while ad_page_contract gets the value from the http var. + So while processing in Tcl that value may change.

    9. How can you get the url of a wizard that is not your current step?

      Index: openacs-4/packages/acs-templating/www/doc/tagref/include.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/tagref/include.html,v diff -u -r1.5.2.2 -r1.5.2.3 --- openacs-4/packages/acs-templating/www/doc/tagref/include.html 22 Jun 2016 07:48:44 -0000 1.5.2.2 +++ openacs-4/packages/acs-templating/www/doc/tagref/include.html 22 Apr 2017 18:30:26 -0000 1.5.2.3 @@ -82,7 +82,7 @@
    10. If the src attribute begins with a slash, the path is assumed to be relative to the server root, the parent directory of - the tcl library. If not, the path is assumed to be relative to the + the Tcl library. If not, the path is assumed to be relative to the current template, not the URL of the page request.