Browsing Russian translation

215.

Some widgets may have different representations depending on the context. For example, the one2many widget can be represented as a form with multiple pages or a multi-columns list.

216.

Events on the widgets module are processed with a callback mechanism. A callback mechanism is a process whereby an element defines the type of events he can handle and which methods should be called when this event is triggered. Once the event is triggered, the system knows that the event is bound to a specific method, and calls that method back. Hence callback.

217.

Module Integrations

218.

The are many different modules available for OpenERP and suited for different business models. Nearly all of these are optional (except ModulesAdminBase), making it easy to customize OpenERP to serve specific business needs. All the modules are in a directory named addons/ on the server. You simply need to copy or delete a module directory in order to either install or delete the module on the OpenERP platform.

219.

Some modules depend on other modules. See the file addons/module/__openerp__.py for more information on the dependencies.

220.

Here is an example of __openerp__.py:

221.

When initializing a module, the files in the init_xml list are evaluated in turn and then the files in the update_xml list are evaluated. When updating a module, only the files from the **update_xml** list are evaluated.

222.

Traditional Inheritance

223.

Objects may be inherited in some custom or specific modules. It is better to inherit an object to add/modify some fields.

224.

It is done with::