Hi, Fri, 1 Feb 2013 11:42:58 +0100 Cédric Krier <[email protected]>: >I think the concept of inherits is buggy as each time we try to use it >on large scale (cf. expense module [1]) it fails because of the >complexity and the impossibility to get a generic behavior that fits >all the needs. IMHO it is good to collect what exactly are 'all the needs' related to inherits?
* My most important need for inherits is the possibility of easy specialization of a view. * The specialization of the model is not important for me, since it can be replaced by many2one. * The shorter name space is not important to me. E.g. Writing 'company.addresses' instead of using the full name space 'company.party.addresses'. Which other needs we have related to inherits? >So as a result, it is almost never used: >... > - company: > Idem as carrier and it could even perhaps improve the > understanding. Here the specialization of party view is very handy. The company view is like '90%' identical to the party view plus some special fields. Is it possible to rebuild this view without inherits? Or is the only way to rebuild the view with function fields that collect data from other models? Regards Udo Spallek -- _____________________________ virtual things Preisler & Spallek GbR München - Aachen Windeckstr. 77 81375 München Tel: +49 (89) 710 481 55 Fax: +49 (89) 710 481 56 [email protected] http://www.virtual-things.biz
signature.asc
Description: PGP signature
