summaryrefslogtreecommitdiff
path: root/addons/web/static/src/js/fields/upgrade_fields.js
AgeCommit message (Collapse)Author
2019-08-07[IMP] *: fix typos in commentsmreficent
closes odoo/odoo#35404 Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
2019-03-06[REF] web: adapt code after jQuery updateVincent Schippefilt
Part of task 1896658 Co-authored-by: Aaron Bohy <aab@odoo.com> Co-authored-by: Christophe Matthieu <chm@odoo.com> Co-authored-by: Mathieu Duckerts-Antoine <dam@odoo.com> Co-authored-by: David Monjoie <dmo@odoo.com> Co-authored-by: Martin Geubelle <mge@odoo.com> Co-authored-by: svs-odoo <svs@odoo.com> Co-authored-by: Vincent Schippefilt <vsc@odoo.com>
2018-11-19[FIX] web: remove debuggerAaron Bohy
closes odoo/odoo#28798
2018-09-21[ADD] partner_autocomplete: Added autocomplete on partners fieldsAntony Lesuisse
For Name field or M2O, gives a list of companies Data comes from Odoo IAP Service
2018-07-27[REF] *: BS4, adapt the label component structureqsm-odoo
The '.label' elements have been replaced by '.badge' elements without the 'badge-pill' class.
2017-09-18[FIX] *: fix a bunch of incorrectly documented docstringXavier Morel
Fix a bunch of ill-documented/incomplete/incorrect method docs Without this, the automatic doc generation does not work.
2017-09-15[MERGE] forward port branch saas-17 up to ed901bedcb7Christophe Simonis
2017-09-15[FIX] web: correctly display the enterprise labelMartin Geubelle
The `upgrade_boolean` widget should display an `Enterprise` label next to it. There is however an issue when a `label` is specified for this field. In this case, the `Enterprise` label should be placed next to the field label (and not the field itself). The easiest solution would have been to instantiate the field widget with its label, but this can't work because the field widget is instantiated before its label. We thus re-render the widget after its label creation.
2017-09-06[FIX] web: Place correctly the enterprise tag for widget upgrade_booleanMahendra barad
2017-06-22[FIX] web: upgrade boolean fields in SettingsSanjay Jamod
Before this rev., there was a traceback when clicking on an upgrade boolean field's checkbox.
2017-04-27[FIX] web: rename `supported_field_types`Martin Geubelle
This key has been renamed `supportedFieldTypes` since the new views but has been wrongly forward-ported in 2e540eb.
2017-04-19[IMP] web: add timezone_mismatch field widgetChristophe Matthieu
* display a warning when the timezone offset is not the same of the browser timezone offset * if different, display the time in the selected timezone
2017-04-11[REF] web: remove old commented codeGéry Debongnie
Also, add some docstring tags.
2017-04-11[REF] web, *: simplify our RPC system (in JS)Géry Debongnie
The RPC system was not completely satisfactory, we decided to prepare the future and do it properly. This commit introduces the new rpc system, which replace the previous new one. We now simply have a method, this._rpc, which takes a dictionary of parameters. The idea is that depending on the parameters, it is able to add correct default value when necessary. For situations where we don't have the this._rpc method, we can use the rpc.query method, which takes the same arguments, but directly calls ajax.rpc instead of triggering up some events.
2017-04-11[REF] *: use _rpc method for all rpcsGéry Debongnie
The _rpc method is now the preferred method to do a rpc, so we need to update all calls.
2017-04-11[FIX] *: apply changes from web_studioAaron Bohy
The new views and widgets (at least some of them) first landed in web_studio (v10), and they we moved later to web, so changes in web_studio need to be applied in web.
2017-04-11[REF] web, *: redesign all JS viewsGéry Debongnie
This commit introduce a full redesign of all JS views. We started basically from scratch. The goal was to unify all the various views under a common framework, to make them testable, to make then usable in different conditions (in studio, or in the frontend), and to make our lives easier. Some important points are: - we introduced new coding guidelines (camelCase, 80 chars width, ...) - we have a brand new testing framework (still QUnit based) - kanban view moved to the web addon - calendar view (formerly web_calender) moved to web as well - the tree view was removed - all new code should be documented We hope that this code is the start of a new era for the Odoo web client, we want to have a high quality codebase, well documented, well tested, well designed. Work done by the framework team: mostly aab, ged, chm, dmo, qsm