Odoo - The current checkout of upstream Odoo

Age	Commit message (Collapse)	Author
2016-08-10	[IMP] various: use odoo for imports instead of openerp and update class names	Thibault Delavallée

2016-07-06	[MIG] decimal_precision: migrate to new API	Xavier Morel

2016-07-05	[FIX] qweb: float widget: use same rounding as orm float field	Christophe Matthieu
	42,12345 with precision=4 should be 42,1235 and not 42,1234
2016-07-05	[IMP] qweb: add t-options on t-esc and t-raw who use 'ir.qweb.field' models	Christophe Matthieu
	Remove 'field' from 'value_to_html' method attributes 't-esc' escape the result of the widget. (Added 'remove_span' as option for monetary widget) E.g.: <t t-esc="32" t-options='t-options='{"widget": "monetary", "display_currency": website.currency_id, "remove_span": True}'> result: $ 365.00
2014-11-04	[IMP] use model._fields instead of model._all_columns to cover all fields	Raphael Collet
	The old-api model._all_columns contains information about model._columns and inherited columns. This dictionary is missing new-api computed non-stored fields, and the new field objects provide a more readable api... This commit contains the following changes: - adapt several methods of BaseModel to use fields instead of columns and _all_columns - copy all semantic-free attributes of related fields from their source - add attribute 'group_operator' on integer and float fields - base, base_action_rule, crm, edi, hr, mail, mass_mailing, pad, payment_acquirer, share, website, website_crm, website_mail: simply use _fields instead of _all_columns - base, decimal_precision, website: adapt qweb rendering methods to use fields instead of columns
2013-10-21	[ADD] decimal precision support to float t-field rendering	Xavier Morel
	bzr revid: xmo@openerp.com-20131021094533-e510uy6byck85xma