On 05/07/10 13:57 +0300, Elver Loho wrote: > Hi, all! > > Got a question regarding extending existing classes (like with _name = > "party.party") and their views (<field name="inherit" > ref="party.party_view_form"/>) > > In what order are these extensions added to the base classes/views? > > For example, suppose that five different modules extended party.party > with additional fields, by hiding existing fields in the view, and > doing other such shenanigans. Is the end result somehow deterministic? > Is the order of these additions/subtractions somehow determined by > some factor?
The order is deterministic [1]. It is the module order (determined by dependencies and alphabetical order) then the priority and finnaly the id. The only part that can differ between to installation is the id but it is hardly advise to extend a view inside a module only once. [1] http://hg.tryton.org/hgwebdir.cgi/trytond/file/9fa480f96eba/trytond/model/modelview.py#l174 -- Cédric Krier B2CK SPRL Rue de Rotterdam, 4 4000 Liège Belgium Tel: +32 472 54 46 59 Email/Jabber: [email protected] Website: http://www.b2ck.com/
pgpnxbZerZ5ip.pgp
Description: PGP signature
