Hi Amit, Yes, I looked at 'attrs' but it only allows you to hide fields on a view. What I'm talking about is the whole idea of inheritance. I've copied below what I posted in the bug:
> When people think of inheriting they think of subclassing an object. What is > really occurring with inherited views is not subclassing. It is a > modification of the parent. So why call it inheritance? > > Another problem is that there is no real inheritance for views. > > What I would like to suggest is that for views, the current 'inherit' be > changed to 'modify' which would make it clear to devs that what is happening > is just a modification of the parent. > > Then a real subclassing of views should be created by using the name > 'inherit'. In this case the referenced parent view is first copied and then > the changes are applied. > > Now when there are underlying changes in base views made they will > automatically be added to all inherited views. If for some reason an anchor > node for an inherited view should get changed and cause an error, well at > least you would know where that happened because you would get a traceback. > And this is far better than today where a base view that you've had to copy > (in order to form a new view) has changed and you receive no indication and > things begin to get out of sync. > > Since v5.0 has broken backwards compatibility already, now would be the best > time to make this change since we have to rewrite our modules anyway for v5.0. Regards, Gerry -------------------- m2f -------------------- -- http://www.openerp.com/forum/viewtopic.php?p=26991#26991 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
