This rev. 06104ba553
Added the dirty flag on the o2m field when the editor of the editable list was enabled (meaning that the editable list has been altered)) because the dirty flag was not set correctly by the one2many during the edition, at the time.
It looks like this is now the case
Besides, as now, we valid all the editable list of the form, wether or not the editable list was altered, we must not set the o2m as dirty anymore.
the buttons edit and create have been ungrouped recently. As a
side effect (of course), the bouncing effect in form view is broken.
This should hopefully fix the issue without introducing any other
problems :/
- stage model (project.task.type): add fields holding the eventual specific
legends for kanban states and star (priority) management
- project: task now have labels; you may use project to hold trainings
instead of tasks.
- project form: use label field on tasks statinfo to use the label
- project.task form: use kanban state customization using states_legend option;
- project.task kanban: use kanban column and kanban state cuztomization
using group_by_tooltip and states_legend options
- project_issue: issues now have labels, like tasks.
- issue: same kanban custo as for tasks
- update data and demo data
[IMP] web: statinfo widget now take an optional label_field option allowing
to have strings coming from another field present in the form view
search bar does not suggest date field format based on user's locale and always shows based on mmddyy using Date.parse, opw:615276
Note: starting in 9.0, datejs has been replaced by momentjs, so this
problem should be solved in a better way.
the filters menu can quickly grow if the user adds many conditions.
Once it grows out of the screen, the lower buttons can not be reached
anymore. This patch adds a vertical scrollbar to fix this issue. It
has to use some javascript to update its max-height property.
Kanban and form view kanban selection widgets can now be dependent of the
current stage of the record. The displayed legend can be taken directly
from the stage instead of the field selection values.
- added states_legend option on kanban selection widget for kanban and form
view: used to change the selection displayed value by a value coming from the
record given by group_by (kanban) / states_legend_field (form view). This allows
customizing the kanban selection widget depending on stages.
Improved the tooltip of kanban groups customization by improving the first
implementation of group_by_tooltip parameter in kanban view declaration.
This is done by adding some options and improving the first (still not
used) implementation:
- added group_by_tooltip option on field used to group on kanban view. Its
values is a collection of fields on the record used to group. The tooltip of
the group header will be the text formed from those fields values, allowing
custom tooltips for different kanban columns.
- now all data of the kanban columns are fetched in one call instead of doing
one call for each column. The various fields to read are collected by
introspecting the view definition.
Future commits will aim at using those features various addons, notably
in recruitment, project and crm.
once widget extended with ReinitializeFieldMixin, the event binding with the binary file input and the on_file_change method can be done in initialize_content instead of start
This fix is related to d36c8b5c9b
The add attachment button should be displayed while being in edit mode, but not in view mode
As the widget depends on the form actual mode, the widget should be re-rendered each time the actual mode changes
This is the point of the ReinitializeFieldMixin class
* add a replace_breadcrumb option to actionmanager
* correctly calls on_reverse_breadcrumbs when needed
* add a semi-protected way to manipulate breadcrumbs (get_widgets)
* calls do_show when changing widgets
To valid all editable list line, we iterate on the lines and set the editor form with the line value, using set_value.
The _inhibit_on_change_flag should be set to True to avoid triggering on changes events
opw-617395
it was trying to call the forme 'hide' method on the searchview. To
solve the problem, I readded the method (and renamed it to do_hide for
consistency with views)
opw-617036:
In my current timesheet, if you add a a required field on the timesheet ids lines, and add data in the summary tab, it was possible to validate the timesheet lines while requried fields were missing.
Christophe Simonis