diff options
| author | Antony Lesuisse <al@openerp.com> | 2014-12-19 02:51:08 +0100 |
|---|---|---|
| committer | Antony Lesuisse <al@openerp.com> | 2014-12-19 04:09:51 +0100 |
| commit | 7c0e598c97cc48d8e55688c99db6d11ee23d9e46 (patch) | |
| tree | 65577c79f42a458f6d5aa48e16102e67360e1dc1 /doc | |
| parent | 9b463a5abe9f5ff92bc70eacaa024bc00c61281a (diff) | |
[IMP] convert.py xml <odoo> parsing and cleanups
- deprecate <url> tag
- deprecate multi levels name for <menuitem>
- <odoo> <openerp> <data> tags are now equivalent and may be nested, it means
that the <data> tag is now optional and should only be used if the same xml
file contains both update and noupdate records.
Only the base_menu.xml has been converted to the new format as an example.
Other files will be be progressively converted to avoid useless conflicts in
forward ports.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/reference/data.rst | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/doc/reference/data.rst b/doc/reference/data.rst index bd98ded3e8b..a53b1fa604b 100644 --- a/doc/reference/data.rst +++ b/doc/reference/data.rst @@ -15,16 +15,15 @@ Structure The main way to define data in Odoo is via XML data files: The broad structure of an XML data file is the following: -* The nested root elements ``openerp`` and ``data`` -* Any number of operation elements within ``data`` +* Any number of operation elements within the root element ``odoo`` .. code-block:: xml <!-- the root elements of the data file --> - <openerp><data> + <odoo> <operation/> ... - </data></openerp> + </odoo> Data files are executed sequentially, operations can only refer to the result of operations defined previously |
