We are talking only about the views here. On the model side the _inherit and _inherits are fine. But, on the view side 'inherit' clearly makes no sense as currently implemented because you are just modifying the parent view. So call it what it is: 'modify'. You are modifying a view. You are not inheriting a view. If you were inheriting, you could make changes and they would not affect the parent view. Why keep bad this terminology in OpenERP?
Now as I said, there is a need to create true inheritance of views not just modification of views in OpenERP. Today you can only somewhat simulate a pseudo inheritance by copying a view and modifying the copy. But this creates no linkage between the parent view and the child view. If the parent view changes, the child has no knowledge of the change. So as I said in the previous posting, the way to do this is to use 'inherit' keyword to mean taking a parent view and making a copy of it, then applying any changes and now you have a child view that is linked to the parent view. As far as template engines, macros, etc., yes, even they know about and use inheritance to form views as you would expect it to mean. So the view system in OpenERP should also do the same. Finally, this change should be done now, not a year from now in some version 6 after thousands of more modules have been written with bad terminology. Regards, Gerry -------------------- m2f -------------------- -- http://www.openerp.com/forum/viewtopic.php?p=27009#27009 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
