| Age | Commit message (Collapse) | Author |
|---|
|
This commit introduces a new module system for the javascript code.
Instead of using global (namespaced) variables everywhere (like
openerp.web.whatever, ...), each file declare one (or more) module
with its dependencies. Each module will be loaded after its
dependencies, and will be given a reference to the return values.
This change is a massive departure from the way the client worked
previously. It will sadly break some/most history, but I am sure that
the future git ecosystem will allow you to easily browse the history
past this revision (one can dream).
This commit feature:
* main namespace is now odoo instead of openerp
* a way to define modules and dependencies (inspired by requirejs)
* many files have been splitted in simpler subfiles
* basic support for debugging in odoo.__DEBUG__
* no global variable (i.e. nothing in window.openerp)
* many bug fixes, many new bugs
Future vision: this modularization should simplify future code
development, simplify debugging and will allow a serious testing effort
|
|
|
|
|
|
|
|
* Fixes the pager on grouped list views for which there was no
specific behavior (except of doing +1 or -1) for next and previous
actions on last and first pages respectively.
* Hides the previous and next buttons of the main pager on grouped list
views as these buttons have no effect in grouped mode.
|
|
When the number of records n and the limit l were such that n%l = 0
(e.g. 16 records total, 8 displayed per page), clicking on the
previous button on the first page, or on the next button on the
last page produced a bug because the total number of pages
computed for this edge case was incorrect.
|
|
|
|
If the list view is grouped (with a groubpy filter),
the default order must always be the order of the groupby
|
|
Empty checkboxes are supposed to be displayed.
Fix specifically and only in the binary field.
|
|
* use new support to colorize reconciled bank statement lines
* fixes tokenization of ``is not`` to not blow up on ``not foo``
* improves calling code to get truthiness of evaluated expression
instead of truthiness of javascript-equivalent objects: an empty list
is falsy in Python but truthy in javascript, since the evaluated
expression is in Python one would expect Python truthiness rules
without having to manually convert to boolean
closes #5070
|
|
ignore .po and .pot changes
|
|
In case of an empty inline column, a Download link inviting the user to
click would still be rendered (erroring out if the user eventually
clicked on it)
fixes #3684
|
|
The sidebar in view pivot was not hidden when switching from view pivot
to another view. Thus, the sidebar content of view pivot was still in a
dropdown of the sidebar of the new view (when this new view has a
sidebar as well).
Also changed the way of switching between views: we now first hide the
current view before creating and displaying the new one. This prevents
weird rendering in the header as well.
Moreover, the task of hidding/showing the view's buttons is left to the
view instead of the ViewManager.
|
|
|
|
closes #4338
closes #3592
|
|
|
|
Broaden the set of conditions where reordering is allowed. Lists can be
reordered when they are sorted by sequence (or sequence ASC)
opw-619465
|
|
|
|
|
|
When the list view is grouped, the page count should be hidden as irrelevant.
However if it's fully hidden, the limit can no longer be changed.
Instead of hidding the pager, this commit hides the arrows and replaces
the content by the current limit to allow to be changed.
|
|
list view hide the pager when it is grouped, but it should show it again
after it is ungrouped.
|
|
|
|
|
|
|
|
See issue #3964 for more detail. Main problem was caused by commit
f0e331e005d8. It set the key name+'__display' to false when reloading
a record for all field types, but it was only concerned with many2many.
|
|
|
|
Fixes the issue #1216 (follow the link for more information). The issue
was caused by a hack in list view: the magical suffix __display is used
in render_cell to determine if a many2many field should be updated. This
commit simply makes sure that old many2many fields + __display keys are
cleared.
A better way would be to redesign/refactor the list view to avoid that
hack in the first place. But this would be a much more complex task.
|
|
|
|
|
|
i am aware that this is an interesting hack, and that i do not resize
correctly the $buttons after the bouncing effect, but at least, it
solves the problem.
|
|
the bouncing is supposed to occur when clicking on the area in view list
with no content. Problem was that the Create button was separated from
the import button while bouncing. This commit fixes the issue in a not
really subtle way: it instead bounces the whole row. I tried to find a
better fix, but I don't like jqueryui and i don't want to spend too much
time on this.
|
|
some small stuff...
|
|
The pager was removed in the refactoring of view manager. This commit
readd the pager, and improves its rendering to avoid flickering
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
dataset
|
|
Missing backport of commit f652402 for buffered dataset
Again, should not be forwardported
|
|
If an action unlink the current records (e.g. unreconcile on account.move.reconcile), trigger history_back to avoid errors when trying to reload inexistant record (opw 607883)
This is a partial backport of saas-4 code (rev c0db6ae, 162ad1c) and should not be forward ported.
|
|
|
|
|
|
|
|
Displaying the pagert in view group does not make sense as it's not updated when changing filter and every group (even if more than 80) is displayed in view group
|
|
|
