On 10/04/13 15:53, Stefan Rijnhart (Therp) wrote:
>> Actually we plan to remove one2many fields from form views
> Fabien, could you please share the location of that branch, so that I
> can see for myself that 'removing one2many fields from form views' is
> not as bad as it sounds?
Sorry, I was not clear.
We do not want to remove one2many. We want to remove one2many fields
that were used for history and replace them by related action button.
Most of
them have already been replaced by buttons in v7.
As an example, on the partner form: Tasks, Meetings, Opportunities, Sales
are not integrated as one2many of the parnter but as a button on the partner
to open these views.
Nearly all of these one2many have already been replaced by buttons in v7.
Only 4 are remaining in the partner form: Campains, Tasks, Events, Claims.
These 4 should be replaced by buttons in v7, like we already did for other
actions.
In the future, I also think that we should add a number, like "4 Sales
Order",
in the button, like we did in the kanban view of partners.
On 10/04/13 15:53, Stefan Rijnhart (Therp) wrote:
>> Actually we plan to remove one2many fields from form views
> Fabien, could you please share the location of that branch, so that I
> can see for myself that 'removing one2many fields from form views' is
> not as bad as it sounds?
Sorry, I was not clear.
We do not want to remove one2many. We want to remove one2many fields
that were used for history and replace them by related action button.
Most of
them have already been replaced by buttons in v7.
As an example, on the partner form: Tasks, Meetings, Opportunities, Sales
are not integrated as one2many of the parnter but as a button on the partner
to open these views.
Nearly all of these one2many have already been replaced by buttons in v7.
Only 4 are remaining in the partner form: Campains, Tasks, Events, Claims.
These 4 should be replaced by buttons in v7, like we already did for other
actions.
In the future, I also think that we should add a number, like "4 Sales
Order",
in the button, like we did in the kanban view of partners.
Fabien