The files describing the views are of the form:
| Example: |
|---|
<newline/>
<?xml version="1.0"?>
<openerp>
<data>
[view definitions]
</data>
</openerp>
- <record> tags with the attribute model=”ir.ui.view”, which contain the view definitions themselves
- <record> tags with the attribute model=”ir.actions.act_window”, which link actions to these views
- <menuitem> tags, which create entries in the menu, and link them with actions
New : You can specify groups for whom the menu is accessible using the groups attribute in the menuitem tag.
New : You can now add shortcut using the shortcut tag.
| Example: |
|---|
<newline/>
<shortcut
name="Draft Purchase Order (Proposals)"
model="purchase.order"
logins="demo"
menu="m"/>
<record model="ir.ui.view" id="v">
<field name="name">sale.order.form</field>
<field name="model">sale.order</field>
<field name="priority" eval="2"/>
<field name="arch" type="xml">
<form string="Sale Order">
.........
</form>
</field>
</record>
<record model="ir.ui.view" id="v">
<field name="name">sale.order.form</field>
<field name="model">sale.order</field>
<field name="priority" eval="2"/>
<field name="arch" type="xml">
<form string="Sale Order">
.........
</form>
</field>
</record>
View Types¶
Tree View¶
You can specify the columns to include in the list, along with some details of the list’s appearance. The search fields aren’t specified here, they’re specified by the select attribute in the form view fields.
<record id="view_location_tree2" model="ir.ui.view">
<field name="name">stock.location.tree</field>
<field name="model">stock.location</field>
<field name="type">tree</field>
<field name="priority" eval="2"/>
<field name="arch" type="xml">
<tree
colors="blue:usage=='view';darkred:usage=='internal'">
<field name="complete_name"/>
<field name="usage"/>
<field
name="stock_real"
invisible="'product_id' not in context"/>
<field
name="stock_virtual"
invisible="'product_id' not in context"/>
</tree>
</field>
</record>
<record id="view_location_tree2" model="ir.ui.view">
<field name="name">stock.location.tree</field>
<field name="model">stock.location</field>
<field name="type">tree</field>
<field name="priority" eval="2"/>
<field name="arch" type="xml">
<tree
colors="blue:usage=='view';darkred:usage=='internal'">
<field name="complete_name"/>
<field name="usage"/>
<field
name="stock_real"
invisible="'product_id' not in context"/>
<field
name="stock_virtual"
invisible="'product_id' not in context"/>
</tree>
</field>
</record>
<record id="view_location_tree" model="ir.ui.view">
<field name="name">stock.location.tree</field>
<field name="model">stock.location</field>
<field name="type">tree</field>
<field name="field_parent">child_ids</field>
<field name="arch" type="xml">
<tree toolbar="1">
<field icon="icon" name="name"/>
</tree>
</field>
</record>
<record id="view_location_tree" model="ir.ui.view">
<field name="name">stock.location.tree</field>
<field name="model">stock.location</field>
<field name="type">tree</field>
<field name="field_parent">child_ids</field>
<field name="arch" type="xml">
<tree toolbar="1">
<field icon="icon" name="name"/>
</tree>
</field>
</record>
- colors
- Conditions for applying different colors to items in the list. The default is black.
- toolbar
- Set this to 1 if you want a tree structure to list the top level entries in a separate toolbar area. When you click on an entry in the toolbar, all its descendants will be displayed in the main tree. The value is ignored for flat lists.
Grouping Elements¶
Notebook¶
<notebook>: With notebooks you can distribute the view fields on different tabs (each one defined by a page tag). You can use the tabpos properties to set tab at: up, down, left, right.
| Example: |
|---|
<newline/>
<notebook colspan="4">....</notebook>
<group>: groups several columns and split the group in as many columns as desired.
- colspan: the number of columns to use
- rowspan: the number of rows to use
- expand: if we should expand the group or not
- col: the number of columns to provide (to its children)
- string: (optional) If set, a frame will be drawn around the group of fields, with a label containing the string. Otherwise, the frame will be invisible.
| Example: |
|---|
<newline/>
<group col="3" colspan="2">
<field name="invoiced" select="2"/>
<button colspan="1" name="make_invoice" states="confirmed" string="Make Invoice"
type="object"/>
</group>
Defines a new notebook page for the view.
| Example: |
|---|
<newline/>
<page string="Order Line"> ... </page>:
Data Elements¶
Field¶
attributes for the “field” tag
- select="1": mark this field as being one of the search criteria for
this resource’s search view. A value of 1 means that the field is included in the basic search, and a value of 2 means that it is in the advanced search.
colspan="4": the number of columns on which a field must extend.
readonly="1": set the widget as read only
required="1": the field is marked as required. If a field is marked as required, a user has to fill it the system won’t save the resource if the field is not filled. This attribute supersede the required field value defined in the object.
nolabel="1": hides the label of the field (but the field is not hidden in the search view).
invisible="True": hides both the label and the field.
password="True": replace field values by asterisks, “*”.
string="": change the field label. Note that this label is also used in the search view: see select attribute above).
- domain: can restrict the domain.
- Example: domain=”[(‘partner_id’,’=’,partner_id)]”
- widget: can change the widget.
- Example: widget=”one2many_list”
- one2one_list
- one2many_list
- many2one_list
- many2many
- url
- image
- float_time
- reference
- mode: sequences of the views when switching.
- Example: mode=”tree,graph”
- on_change: define a function that is called when the content of the field changes.
- Example: on_change=”onchange_partner(type,partner_id)”
- See ViewsSpecialProperties for details
- attrs: Permits to define attributes of a field depends on other fields of the same window. (It can be use on page, group, button and notebook tag also)
- Format: “{‘attribute’:[(‘field_name’,’operator’,’value’),(‘field_name’,’operator’,’value’)],’attribute2’:[(‘field_name’,’operator’,’value’),]}”
- where attribute will be readonly, invisible, required
- Default value: {}.
- Example: (in product.product)
- select="1": mark this field as being one of the search criteria for
this resource’s search view. A value of 1 means that the field is included in the basic search, and a value of 2 means that it is in the advanced search.
colspan="4": the number of columns on which a field must extend.
readonly="1": set the widget as read only
required="1": the field is marked as required. If a field is marked as required, a user has to fill it the system won’t save the resource if the field is not filled. This attribute supersede the required field value defined in the object.
nolabel="1": hides the label of the field (but the field is not hidden in the search view).
invisible="True": hides both the label and the field.
password="True": replace field values by asterisks, “*”.
string="": change the field label. Note that this label is also used in the search view: see select attribute above).
- domain: can restrict the domain.
- Example: domain=”[(‘partner_id’,’=’,partner_id)]”
- widget: can change the widget.
- Example: widget=”one2many_list”
- one2one_list
- one2many_list
- many2one_list
- many2many
- url
- image
- float_time
- reference
- mode: sequences of the views when switching.
- Example: mode=”tree,graph”
- on_change: define a function that is called when the content of the field changes.
- Example: on_change=”onchange_partner(type,partner_id)”
- See ViewsSpecialProperties for details
- attrs: Permits to define attributes of a field depends on other fields of the same window. (It can be use on page, group, button and notebook tag also)
- Format: “{‘attribute’:[(‘field_name’,’operator’,’value’),(‘field_name’,’operator’,’value’)],’attribute2’:[(‘field_name’,’operator’,’value’),]}”
- where attribute will be readonly, invisible, required
- Default value: {}.
- Example: (in product.product)
<field digits="(14, 3)" name="volume" attrs="{'readonly':[('type','=','service')]}"/>
eval: evaluate the attribute content as if it was Python code (see below for example)
default_focus: set to 1 to put the focus (cursor position) on this field when the form is first opened. There can only be one field within a view having this attribute set to 1 (new as of 5.2)
<field name="name" default_focus=”1”/>
Here’s the source code of the view of a sale order object. This is the same object as the object shown on the screen shots of the presentation.
| Example: |
|---|
<newline/>
<?xml version="1.0"?>
<openerp>
<data>
<record id="view_partner_form" model="ir.ui.view">
<field name="name">res.partner.form</field>
<field name="model">res.partner</field>
<field name="type">form</field>
<field name="arch" type="xml">
<form string="Partners">
<group colspan="4" col="6">
<field name="name" select="1"/>
<field name="ref" select="1"/>
<field name="customer" select="1"/>
<field domain="[('domain', '=', 'partner')]" name="title"/>
<field name="lang" select="2"/>
<field name="supplier" select="2"/>
</group>
<notebook colspan="4">
<page string="General">
<field colspan="4" mode="form,tree" name="address"
nolabel="1" select="1">
<form string="Partner Contacts">
<field name="name" select="2"/>
<field domain="[('domain', '=', 'contact')]" name="title"/>
<field name="function"/>
<field name="type" select="2"/>
<field name="street" select="2"/>
<field name="street2"/>
<newline/>
<field name="zip" select="2"/>
<field name="city" select="2"/>
<newline/>
<field completion="1" name="country_id" select="2"/>
<field name="state_id" select="2"/>
<newline/>
<field name="phone"/>
<field name="fax"/>
<newline/>
<field name="mobile"/>
<field name="email" select="2" widget="email"/>
</form>
<tree string="Partner Contacts">
<field name="name"/>
<field name="zip"/>
<field name="city"/>
<field name="country_id"/>
<field name="phone"/>
<field name="email"/>
</tree>
</field>
<separator colspan="4" string="Categories"/>
<field colspan="4" name="category_id" nolabel="1" select="2"/>
</page>
<page string="Sales & Purchases">
<separator string="General Information" colspan="4"/>
<field name="user_id" select="2"/>
<field name="active" select="2"/>
<field name="website" widget="url"/>
<field name="date" select="2"/>
<field name="parent_id"/>
<newline/>
</page>
<page string="History">
<field colspan="4" name="events" nolabel="1" widget="one2many_list"/>
</page>
<page string="Notes">
<field colspan="4" name="comment" nolabel="1"/>
</page>
</notebook>
</form>
</field>
</record>
<menuitem
action="action_partner_form"
id="menu_partner_form"
parent="base.menu_base_partner"
sequence="2"/>
</data>
</openerp>
The eval attribute¶
Normally, content inside <field> tags are always evaluated as strings.
- Example 1:
<field name="value">2.3</field>
<field name="value">2.3</field>
- Example 2:
<field name="value">False</field>
<field name="value">False</field>
If you want to evaluate the value to a float, a boolean or another type, except string, you need to use the eval attribute:
<field name="value" eval="2.3" />
<field name="value" eval="False" />
<field name="value" eval="2.3" />
<field name="value" eval="False" />
Adds a button to the current view. Allows the user to perform various actions on the current record.
After a button has been clicked, the record should always be reloaded.
Buttons have the following attributes:
- @type
- Defines the type of action performed when the button is activated:
- workflow (default)
- The button will send a workflow signal [1] on the current model using the @name of the button as workflow signal name and providing the record id as parameter (in a list).
The workflow signal may return an action descriptor, which should be executed. Otherwise it will return False.
- object
- The button will execute the method of name @name on the current model, providing the record id as parameter (in a list). This call may return an action descriptor to execute.
- action
- The button will trigger the execution of an action (ir.actions.actions). The id of this action is the @name of the button.
From there, follows the normal action-execution workflow.
- @special
- Only has one possible value currently: cancel, which indicates that the popup should be closed without performing any RPC call or action resolution.
Note
Only meaningful within a popup-type window (e.g. a wizard). Otherwise, is a noop.
Warning
@special and @type are incompatible.
Note
Only meaningful within a popup-type window (e.g. a wizard). Otherwise, is a noop.
Warning
@special and @type are incompatible.
- @confirm
- A confirmation popup to display before executing the button’s task. If the confirmation is dismissed the button’s task must not be executed.
- @string
- The label which should be displayed on the button [2].
- @icon
- Display an icon on the button, if absent the button is text-only [3].
- @states, @attrs, @invisible
- Standard OpenERP meaning for those view attributes
- @default_focus
- If set to a truthy value (1), automatically selects that button so it is used if RETURN is pressed while on the form.
May be ignored by the client.
New in version 6.0.
| Example: |
|---|
<newline/>
<button name="order_confirm" states="draft" string="Confirm Order" icon="gtk-execute"/>
<button name="_action_open_window" string="Open Margins" type="object" default_focus=”1”/>
Adds a simple label using the string attribute as caption.
| Example: |
|---|
<newline/>
<label string="Test"/>
Force a return to the line even if all the columns of the view are not filled in.
| Example: |
|---|
<newline/>
<newline/>
| [1] | in form view, in list view buttons have no label |
| [2] | behavior in list view is undefined, as list view buttons don’t have labels. |
| [3] | behavior in list view is undefined, as list view buttons don’t have labels. |