odoo
/
odoo
2
0
Fork 0
Code Pull Requests Releases Activity

[DOC] minor wording/formatting/nitpicking on top of previous patch 

bzr revid: odo@openerp.com-20130821115822-kd9d8m1upvo5wiux
This commit is contained in:
Olivier Dony 2013-08-21 13:58:22 +02:00
parent 7ce2c64eb4
commit c57b85ed53
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/03_module_dev_03.rst
View File

@ -1351,21 +1351,22 @@ When you add a one2many field in a form view, you do something like this :
If you want to specify the views to use, you can add a *context* attribute, and
specify a view id for each type of view supported, exactly like the action's
*view_id* attribute:
*view_id* attribute, except that the provided view id must always be
fully-qualified with the module name, even if it belongs to the same module:
.. code-block:: xml
<field name="order_line" colspan="4" nolabel="1"
context="{'form_view_ref' : 'module.view_id',
'tree_view_ref' : 'module.view_id'}"/>
context="{'form_view_ref': 'module.view_id',
'tree_view_ref': 'module.view_id'}"/>
.. note::
You have to put the module name in xml id of the view, because this
You *have to* put the module name in the view_id, because this
is evaluated when the view is displayed, and not when the XML file
is parsed, so the module name information is not available. Failing
to do so will result in the default view being selected (see
below).
below).
If you don't specify the views, OpenERP will choose one in this order :