There is absolutely no consistency with regards to terminology and naming
conventions (maybe it is a translation challenge). This makes it unnecessarily
complicated to try and figure out how things work. Not to mention the total
confusion for end users. Worst of all, these are certified modules.
Is there some documentation somewhere that explain all this or must people just
miraculously figure this out.
Is this addressed in new versions, or part of some QA activity.
See this example. The user see "Delivery Method"
* It means (totaly) different things.
* The user see different possible values.
* The help messages are even more confusing.
* Developer nightmare, different names for the same thing.
* These are certified modules.
sale/sale.py
class sale_order(osv.osv):
'picking_policy': fields.selection([('direct', 'Partial Delivery'),
('one', 'Complete Delivery')], 'Packing Policy', required=True,
help="""If you don't have enough stock available to deliver all at
once, do you accept partial shipments or not?"""),
class sale_config_picking_policy(osv.osv_memory):
'picking_policy': fields.selection([('direct', 'Direct Delivery'),
('one', 'All at Once') ], 'Packing Default Policy', required=True),
stock.stock.py
class stock_picking(osv.osv):
'move_type': fields.selection([('direct', 'Direct Delivery'), ('one',
'All at once')], 'Delivery Method', required=True),
delivery/partner.py
class res_partner(osv.osv):
'property_delivery_carrier': ... string="Delivery Method" ... help="This
delivery method will be used when invoicing from packing.
delivery/sale.py
class sale_order(osv.osv):
'carrier_id':fields.many2one("delivery.carrier","Delivery method",
help="Complete this field if you plan to invoice the shipping based on
packing."),
-------------------- m2f --------------------
--
http://www.openobject.com/forum/viewtopic.php?p=60590#60590
-------------------- m2f --------------------
_______________________________________________
Tinyerp-users mailing list
http://tiny.be/mailman2/listinfo/tinyerp-users
