1.1 --- a/docs/JavaScript-reference.html Fri Nov 21 01:43:03 2008 +0100
1.2 +++ b/docs/JavaScript-reference.html Fri Nov 21 01:43:30 2008 +0100
1.3 @@ -12,7 +12,7 @@
1.4 <pre>'platforms'</pre>
1.5 The above example causes an update to be sent to the location <code>platforms</code> relative to the current page.</dd><dt><code>sourceAreasStr</code></dt><dd>A comma-separated list of regions in the form data which affect the outcome of the update. For example:<br />
1.6 <pre>'/package$1/platforms$1'</pre>
1.7 -Typically, one would use an <a href="../apidocs/public/XSLForms.Output-module.html">template extension function</a> to provide such information. For example:<br />
1.8 +Typically, one would use an <a href="../apidocs/XSLForms.Output-module.html">template extension function</a> to provide such information. For example:<br />
1.9 <pre>'{template:other-elements(..)}'</pre>
1.10 Selector fields may be specified in addition to regions:<br />
1.11 <pre>'{template:selector-name('remove_platform', .)}'</pre>
1.12 @@ -20,6 +20,6 @@
1.13 <h2>requestUpdate</h2>
1.14 <p>Parameters:</p><dl><dt><code>url</code></dt><dd>The URL (which may be relative to the current page or resource) to which the update shall be sent. See the description of the <code>url</code> parameter for the <code>requestUpdateArea</code> function for more details.</dd><dt><code>fieldNamesStr</code></dt><dd>A comma-separated list of fields in the form data which affect the outcome of the update. For example:<br />
1.15 <pre>'/package$1/name'</pre>
1.16 -Typically, one would use an <a href="../apidocs/public/XSLForms.Output-module.html">template extension function</a> to provide such information. For example:<br />
1.17 +Typically, one would use an <a href="../apidocs/XSLForms.Output-module.html">template extension function</a> to provide such information. For example:<br />
1.18 <pre>'{template:other-attributes('name', .)}'</pre>
1.19 The above example causes the field associated with the <code>name</code> attribute on the current element to be included in the update.</dd><dt><code>targetName</code></dt><dd>The element identifier (specified by an HTML or XML <code>id</code> attribute) within which the outcome of the update shall appear.</dd><dt><code>targetFieldNamesStr</code></dt><dd>A comma-separated list of fields in the form data which are affected by the update. See the <code>fieldNamesStr</code> parameter for more details.</dd><dt><code>elementPath</code></dt><dd>A simple path into the form data, defining the scope of the update.</dd></dl></body></html>