summaryrefslogtreecommitdiff
path: root/addons/web/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js
diff options
context:
space:
mode:
authorJérome Maes <jem@openerp.com>2016-06-28 16:37:43 +0200
committerJérome Maes <jem@openerp.com>2016-07-14 14:04:34 +0200
commit95938118c751c3e0010e6008c5391fce8c7124e4 (patch)
tree1e889d00b553eb1bfcc2a85afa6f1b105608925f /addons/web/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js
parent5040719b8d9657eb6fd72cb908c97d1e0390202e (diff)
[REF] calendar: change computed fields for start and stop dates
- `start` and `stop` fields are not computed anymore. Indeed, it was not normal to have required stored computed field. Normally we shouldn't write on these fields, but since client calendar api need them, we keep them as normal datetime fields - `start_date` and `stop_date` become stored computed date fields depending of `start`,`stop` and `allday`. An inverse method allow to write on these fields, since it can be the case from the form view - `start_datetime` and `stop_datetime` follow the same logic - `onchange_allday` code is mostly moved in `_inverse_dates` of new computed fields - `_set_date` method (called in create/write) is now removed, since it does the same thing as old onchanges - `_onchange_duration` is kept to adapt `stop_datetime` when changing `start_datetime` or `duration` on form view - Duration is now 'zero' in database for allday meeting. Before, it was not changed. Setting it to zero is less falsy. `duration` can not (yet) be a computed field since it depends on others computed fields. After migration, we manage to keep old behavior but the code was crap. Switching stored computed fields make it cleaner, and respecting new API standarts. This changes avoid multiple methods doing almost the same thing, and is less 'buggy'.
Diffstat (limited to 'addons/web/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js')
0 files changed, 0 insertions, 0 deletions