Great suggestion, I was just fighting with the stock.picking views this week.
It would have been a lot easier if I had known about this feature.
Thanks for writing it up, Thibaut DIRLIK.
** Changed in: openobject-doc
Status: Fix Committed => Fix Released
--
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/658382
Title:
[trunk] missing documentation "form_view_ref"
Status in OpenERP Documentation:
Fix Released
Bug description:
IMHO
http://doc.openerp.com/developer/2_6_views_events/views/design_element.html?highlight=one2many_list
should mention that it is possible to use form_view_ref (and tree_view_ref ?)
in context.
this will make it much easier to code custom modules without
interfering with the standard "priority" model, especially when it
comes to models with a grat number of views like stock.picking
found a single instance of this in
./sale/sale_view.xml: <field colspan="4"
name="invoice_ids" nolabel="1"
context="{'form_view_ref':'account.invoice_form'}"/>
_______________________________________________
Mailing list: https://launchpad.net/~c2c-oerpscenario
Post to : [email protected]
Unsubscribe : https://launchpad.net/~c2c-oerpscenario
More help : https://help.launchpad.net/ListHelp
