Odoo/addons/decimal_precision/tests/test_qweb_float.py, branch 14.0 The current checkout of upstream Odoo [IMP] decimal_precision: integrate into base 2019-07-03T11:15:48+00:00 Mitali Patel mpa@odoo.com 2018-08-13T12:43:30+00:00 0c5121a979f02d6eee9779068cbb2d43788dc917 The decimal precision feature makes sense to be an ORM feature, no need to be in a specific module Previous syntax was from odoo.addons import decimal_precision as dp fields.Float(digits=dp.get_precision('Foo')) and now is: fields.Float(digits='Foo') Remove the possibility to have a callable method on the digits attribute (it was only used for precision anyway) and directly retrieve the digits on the decimal.precision model Rename the method digits to get_digits to avoid confusion between the field attribute when declaring a field and the method to retrieve the precision Task id: 48198 
The decimal precision feature makes sense to be an ORM feature, no need to be
in a specific module

Previous syntax was
    from odoo.addons import decimal_precision as dp
    fields.Float(digits=dp.get_precision('Foo'))

and now is:
    fields.Float(digits='Foo')

Remove the possibility to have a callable method on the digits attribute (it
was only used for precision anyway) and directly retrieve the digits on the
decimal.precision model

Rename the method digits to get_digits to avoid confusion between the field
attribute when declaring a field and the method to retrieve the precision

Task id: 48198
 [IMP] various: use odoo for imports instead of openerp and update class names 2016-08-10T13:48:07+00:00 Thibault Delavallée tde@openerp.com 2016-08-09T14:17:17+00:00 c8a313d51e57e9db52758a2c92c13044efef5a6a 






[MIG] decimal_precision: migrate to new API
2016-07-06T15:19:44+00:00

Xavier Morel
xmo@odoo.com

2016-06-06T17:02:41+00:00

df4508635c413cdb70bdd3b43cbfa368b1bad7a4












[FIX] qweb: float widget: use same rounding as orm float field
2016-07-05T16:43:10+00:00

Christophe Matthieu
chm@odoo.com

2016-07-04T10:59:41+00:00

339d5b85059a191702e479b29471903042144139

42,12345 with precision=4 should be 42,1235 and not 42,1234





42,12345 with precision=4 should be 42,1235 and not 42,1234







[IMP] qweb: add t-options on t-esc and t-raw who use 'ir.qweb.field' models
2016-07-05T16:43:09+00:00

Christophe Matthieu
chm@odoo.com

2016-06-30T14:16:40+00:00

3407fb70e4a5b16174234d10d97710572b6f808c

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





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







[IMP] use model._fields instead of model._all_columns to cover all fields
2014-11-04T12:47:57+00:00

Raphael Collet
rco@openerp.com

2014-11-03T15:00:50+00:00

f2e4a10e1a58c932f9a989e642771f5ae75d756a

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





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







[ADD] decimal precision support to float t-field rendering
2013-10-21T09:45:33+00:00

Xavier Morel
xmo@openerp.com

2013-10-21T09:45:33+00:00

ff07f6dcdd537563030057bb9fbc8a0cc0b6fd81

bzr revid: xmo@openerp.com-20131021094533-e510uy6byck85xma




bzr revid: xmo@openerp.com-20131021094533-e510uy6byck85xma