<p>Provide QWEB templating for formatting some fields.</p> <p>Since version 8.0, this is less usefull as whole form can be templated. But in list views, it's still very much constrained, and this module make sense.</p> <a name="form"></a> <h2>Form</h2> <a name="general-usage"></a> <h3>General usage</h3> <p>In forms, by specifying the correct <code>widget</code>, the XML content of the <code>field</code> will then be interpreted by QWEB (the javascript version):</p> <pre> <code>... &lt;field name=&quot;foo&quot; widget=&quot;many2one_template&quot;&gt; &lt;!-- QWEB template, with 'record' being the m2o targetted record --&gt; &lt;/field&gt; ...</code> </pre> <p>Depending on the widget, you'll get some environment variable already filled with target data. For instance any <code>*2m</code> will receive <code>records</code> the list of targetted values, and any <code>*2o</code> will receive <code>record</code> the targetted value.</p> <a name="widgets"></a> <h3>Widgets</h3> <p>These are the form widget available and the given template vars:</p> <ul class="simple"> <li><code>one2many_template</code> with inner <code>records</code> variable.</li> <li><code>many2one_template</code> with inner <code>record</code> variable.</li> <li><code>many2many_template</code> with inner <code>records</code> variable.</li> <li><code>template</code> with inner <code>value</code>.</li> </ul> <a name="list"></a> <h2>List</h2> <p>In list, there's only one widget called <code>template</code> and the XML content of the <code>field</code> will then be interpreted by QWEB (the javascript version):</p> <pre> <code>... &lt;field name=&quot;foo&quot; widget=&quot;template&quot;&gt; &lt;!-- QWEB template, with 'value' being the value - *2o: value is the target record. - *2m: value is the array of records. - other: value is the direct value --&gt; &lt;/field&gt; ...</code> </pre>