On 04/10/2013 03:06 PM, Fabien (Open ERP) wrote:
> Actually we plan to remove one2many fields from form views, it was a bad
> usability approach. (we already have a branch that removed all remaining
> in trunk) We removed a lot of them in v7 and replaced them by buttons in
> the top right corner.
As you probably guessed, Fabien was talking about one2many fields on the
*Partner form* view, and similar cases where the one2many field does not
represent a parent-child relationship. In many of these cases this [reverse]
o2m relationship was only added to the model as a way to embed a list of
"related items" in the form view. The idea is that those o2m relationships do
not need to be materialized and are best accessed as "related links",
previously located in the sidebar and now also as buttons in the form view.
On 04/10/2013 03:06 PM, Fabien (Open ERP) wrote:
> Actually we plan to remove one2many fields from form views, it was a bad
> usability approach. (we already have a branch that removed all remaining
> in trunk) We removed a lot of them in v7 and replaced them by buttons in
> the top right corner.
As you probably guessed, Fabien was talking about one2many fields on the
*Partner form* view, and similar cases where the one2many field does not
represent a parent-child relationship. In many of these cases this [reverse]
o2m relationship was only added to the model as a way to embed a list of
"related items" in the form view. The idea is that those o2m relationships do
not need to be materialized and are best accessed as "related links",
previously located in the sidebar and now also as buttons in the form view.