1.1 --- a/docs/advice.html Thu Nov 10 19:49:35 2005 +0000
1.2 +++ b/docs/advice.html Fri Nov 11 17:14:22 2005 +0000
1.3 @@ -13,7 +13,7 @@
1.4 <h2>Beware of Nesting Elements in Multiple-Choice Elements</h2>
1.5 <p>It is not necessarily a good idea to nest elements inside
1.6 multiple-choice elements like this:</p>
1.7 -<pre><multi><br /> <multi-enum value="1"/><br /> <multi-enum value="1"/><br /> <multi-enum value="1"/><br /> <nested value="x"/><br /></multi></pre>
1.8 +<pre><multi><br /> <multi-enum value="1"/><br /> <multi-enum value="2"/><br /> <multi-enum value="3"/><br /> <nested value="x"/><br /></multi></pre>
1.9 <p>The reason for this is that the number of multiple-choice values may
1.10 vary within your application, and the nested elements will appear
1.11 at a different position depending on how many such values have been
1.12 @@ -21,8 +21,8 @@
1.13 to begin with, the usage of more advanced features (<a href="in-page-updates.html">in-page updates</a>, for example) will
1.14 probably expose
1.15 problems due to the way XSLForms reconstructs the XML document data
1.16 -from the input form data.</p>
1.17 -<h2>Beware of Adding Elements into Mixtures of Elements</h2>
1.18 +from the input form data.</p><p>We can avoid the above mistake by specifying the first parameter in the <code>template:multiple-choice-field</code> and <code>template:multiple-choice-list-field</code> annotations. For example:</p><pre><select name="..." template:multiple-choice-field="multi,multi-enum,value"><br /> <option value="..." template:multiple-choice-value="multi-enum,value,selected"></option><br /></select></pre>
1.19 +<p>This effectively prevents us from inserting the <code>nested</code> element inside the <code>multi</code> element.<br /></p><h2>Beware of Adding Elements into Mixtures of Elements</h2>
1.20 <p>Although we ignore this rule with the example in this documentation,
1.21 it is necessary to be aware of problems with adding and removing
1.22 elements where other elements may reside. Consider part of our form