95de9e8cb4
There are cases where several objects would like to use a single view, but by default they cannot because a view belongs to only one model. With this change, it becomes possible to do inheritance "by copy", reusing a view from another model without having to redefine it, just by specifying its view_id in the relevant actions. If the original view needs to be modified, it is also possible to explicitly inherit the parent view from the other model, and the effect will be what is expected: the child view can be specified in an action, and will be the result of the inheritance applied on the parent view; but on the other hande the parent view itself is unaffected when used in the context of its own model. bzr revid: odo@openerp.com-20110221172757-qepq5osjqgd9uf8x |
||
|---|---|---|
| addons | ||
| bin | ||
| debian | ||
| doc | ||
| man | ||
| openerp | ||
| pixmaps | ||
| python25-compat | ||
| sql | ||
| tools | ||
| win32 | ||
| .bzrignore | ||
| LICENSE | ||
| MANIFEST.in | ||
| README | ||
| openerp-server.py | ||
| rpminstall_sh.txt | ||
| setup.cfg | ||
| setup.nsi | ||
| setup.py | ||
| ssl-cert.cfg | ||
README
About OpenERP --------------- OpenERP is a free Enterprise Resource Planning and Customer Relationship Management software. It is mainly developed to meet changing needs. The main functional features are: CRM & SRM, analytic and financial accounting, double-entry stock management, sales and purchases management, tasks automation, help desk, marketing campaign, ... and vertical modules for very specific businesses. Technical features include a distributed server, flexible workflows, an object database, dynamic GUIs, customizable reports, NET-RPC and XML-RPC interfaces, ... For more information, please visit: http://www.openerp.com