Apply a z-index of 1051 (bootstrap'smodals are 1050). This fixes
an issue with the many2one hidden in a modal. Also, removed a
reference to a removed file.
- this time it's the restaurant module that has been refactored
- the point of sale extensions points have been reviewed to be more
constistent and allow conditional extensions.
- the chrome subwidgets are instanciated before screens, so that
screens can manipulate them if needed.
- openerp.point_of_sale.load_models([...]) allow to add models to be
loaded at the start of te pos
- openerp.point_of_sale.load_fields(model,fields) allow to add fields
to be loaded for the models.
- message and comment have been renamed to title and body
- refactored the popups to remove duplicated code
- a few css bugfixes for retina displays. (but css is still a mess)
- (unrelated) set a background on body for less white on startup
- This is the first pass of a big cleanup. This breaks
all backward compatibility of pos .js extensions.
- PosWidget has been renamed to 'Chrome'. The Chrome is both
the root widget but also a reference to all chrome subwidgets.
It is the V of MVC.
- ScreenSelector has been renamed to 'Gui'. The Gui contains
the method to manipulate the user interface by changing
screens and instanciating popups. It is the C of MVC
- PosModel is still the root model, the M of MVC
- All these objects are available to all Pos objects trough the
.pos .chrome and .gui references. This is very practical, but
usually you should not need to refer to the chrome or to the
gui in your models. And you should also minimize references
to .chrome, which should be manipulated via .gui
- The Popups, Screens, and Widgets are now declared declaratively
in the Chrome prototype for easier extension by external modules
- You can hook yourself into the various loading steps trough
deferreds:
- pos.ready -> All models have been loaded
- chrome.started -> The chrome dom is inserted but incomplete
- chrome.ready -> The pos is fully rendered and ready to use
- The Chrome subwidgets are available trough .widget
ex: pos_widget.numpad -> chrome.widget.numpad
- The GUI api has been changed a bit :
- set_current_screen -> .show_screen
- Old behavior: each page with such a modifier was first set
invisible at creation of the InvisibiliyChanger attached to
it, and then, after domain evaluation, the page was reset
to visible if needed.
- New behavior: wait for the domain evaluation to decide to set
a page invisible. It also fixes a bug when 2 pages where
active simultaneously. Moreover, we only switch to a newly
displayed page if we are in edit mode (use case: we edited
a field making the page's domain true, so we want the user
to pay attention to this page).
This view was intended to extend the tree view of mrp.bom, not
mrp.bom.line. Nonetheless, the view mrp.mrp_bom_tree_view which is extended here is a
view for a mrp.bom.line, and there is no tree view for a mrp.bom.
So this extension has no meaning anymore and seems to have worked only
by accident...
linting views.js revealed some problems. Most of them minor, but
some of them more serious: redeclared variables in if clauses can
shadow the outer variable, or not. It is fragile, and will cause bugs
if the code is refactored.
Remove old source_id
Use hr.recruitment.source to generate link with utm and create
alias with default value for utm
[FIX] crm/utm: Fix bug with utm (ddac26cdbb)
Move demo into data
Move ir_http to save the utm in the dispatch
- simplifed name of vehicle model; the name is now the model name; the old function
is used to compute the name_get.
- added Suzuki data
- parent of a cost is now hidden except for technical group, because it is the
same as the vehicle
- fixed some vehicule -> vehicle typos
context and no specific order, order on limited leaves then on remaining leaves.
This is usefull for users having their normal leaves being displayed in top of
the list (legal leaves, compensatory leaves, then sick and unpaid for example).
Also updated the name_get of holidays status, displaying (remaining leaves /
max leaves) instead of (taken leaves / max leaves). What is important for
users is the number of remaining leaves, not the number of leaves already
taken in that type.
Also updated and reindented demo data (compensatory is now limited + order
of declaration due to this change).
Yannick Tivisse