What is the use of ir.ui.menu in OpenERP 7.0?

I am new to OpenERP and I wish to know about that what is model="ir.ui.menu" in OpenERP. Like this there are many other models also there.

For eg:

model="ir.ui.view"

model="ir.actions.act_window"

Can any one explain all this?

Solution

With the ir.ui.menu model you can create new menu items. You can use the menuitem tag, it is shortcut:

<record id="menu_human_readable_name" model="ir.ui.menu" >
    <field name="name">Human readable name</field>
    <field name="sequence" eval="10" />
    <field name="action" ref="action_name" />
    <field name="parent_id" ref="base.menu_custom" />
</record>

And you have a small explanation of the ir.actions.act_window model in the Odoo documentation. You can assign the id of this kind of action in the field action of the ir.ui.menu model

The most common action type, used to present visualisations of a model through views: a window action defines a set of view types (and possibly specific views) for a model (and possibly specific record of the model).

<record id="action_human_readable_name_act_window" model="ir.actions.act_window">
    <field name="type">ir.actions.act_window</field>
    <field name="name">Human readable name</field>
    <field name="res_model">model.name</field>
    <field name="view_mode">tree,form</field>
    <field name="view_type">form</field>
    <field name="target">current</field>
    <field name="domain">[]</field>
    <field name="context">{}</field>
    <field name="search_view_id" ref="ir.ui.view" />
</record>

The ir.ui.view is used for the views where you show the field or tree list

You have more information in the Odoo Documentation:

Views define the way the records of a model are displayed. Each type of view represents a mode of visualization (a list of records, a graph of their aggregation, …). Views can either be requested generically via their type (e.g. a list of partners) or specifically via their id. For generic requests, the view with the correct type and the lowest priority will be used (so the lowest-priority view of each type is the default view for that type).

<record model="ir.ui.view" id="view_id">
    <field name="name">view.name</field>
    <field name="model">object_name</field>
    <field name="priority" eval="16"/>
    <field name="arch" type="xml">
        <!-- view content: <form>, <tree>, <graph>, ... -->
        [...]
        <field name="field_name" />
        [...]
    </field>
</record>