c2c-oerpscenario team mailing list archive

[Thibaut DIRLIK <703875@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Currently, the sale.order.line form view (which is used in every
sale.order) is defined as a subview : directly inside its one2many
field. This is not a good thing because you ca't inherit/extend it
without have to inherit the sale.order form view.

Example :

If you want to create a rent.order.line model (which inherits
sale.ordeR.line), to manage rent orders, you can't use the view defined
for sale.order.line.

Fix proposal :

The view should be defined as a plain view, with an XMLID, and specified
with 'form_view_ref' in the context of the one2many field. This way,
modules would inherit only this view.

Problem :

It might break some module that extended the sale.order form view to
edit sale order line form.

** Affects: openobject-server
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/703875

Title:
  Make sale.order.line form view a real view

Status in OpenObject Server:
  New

Bug description:
  Currently, the sale.order.line form view (which is used in every
  sale.order) is defined as a subview : directly inside its one2many
  field. This is not a good thing because you ca't inherit/extend it
  without have to inherit the sale.order form view.

  Example :

  If you want to create a rent.order.line model (which inherits
  sale.ordeR.line), to manage rent orders, you can't use the view
  defined for sale.order.line.

  Fix proposal :

  The view should be defined as a plain view, with an XMLID, and
  specified with 'form_view_ref' in the context of the one2many field.
  This way, modules would inherit only this view.

  Problem :

  It might break some module that extended the sale.order form view to
  edit sale order line form.