Odoo/addons/barcodes/static/src/js/inherited_form_widget_button.js, branch 14.0 The current checkout of upstream Odoo [REF] barcode, *: update code to new JS framework 2017-04-11T17:44:38+00:00 Christophe Matthieu chm@odoo.com 2017-03-29T15:25:18+00:00 920df597d3d7174723736a395e94dc8ff413c70b With the new views, the barcode mechanisms were completely broken, because the view and widget JS code was totally changed. This commit update and refactor all that code to make it work with the new design philosophy. Also, it update the coding style. 
With the new views, the barcode mechanisms were completely broken,
because the view and widget JS code was totally changed.

This commit update and refactor all that code to make it work with the
new design philosophy.  Also, it update the coding style.
[REF] web, *: redesign all JS views 2017-04-11T17:44:38+00:00 Géry Debongnie ged@odoo.com 2017-03-05T09:05:56+00:00 905e01921f3c3ef43ace6fc537d1d8c0d280002c 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 
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
[FIX] stock_barcode: correctly check when to execute "O-BTN" 2016-08-16T16:28:23+00:00 Simon Lejeune sle@openerp.com 2016-08-16T16:28:23+00:00 dbe90c26611fbc062cd38df0235bae78cbe4e898 It's possible to trigger click on form view's button with the help of the "barcode_trigger" attributes. However, we don't want to be able to execute clicks on items that aren't clickable by the user. That's why we wrote the following condition: if the elem is visible OR is a child of a .dropdown-menu, we trigger the click. The second condition was always true since we used the jquery's parent function which return an empty list when no result, and an empty list is truthy. 
It's possible to trigger click on form view's button with the help
of the "barcode_trigger" attributes. However, we don't want to be
able to execute clicks on items that aren't clickable by the user.
That's why we wrote the following condition: if the elem is visible
OR is a child of a .dropdown-menu, we trigger the click.

The second condition was always true since we used the jquery's
parent function which return an empty list when no result, and
an empty list is truthy.
[FIX] barcodes: also allow barcodes triggering buttons in dropdowns 2016-05-10T10:59:37+00:00 Joren Van Onder jov@odoo.com 2016-05-10T09:08:46+00:00 28a9336ac827da0cfd100793ef7f0347c964fed7 On smaller screens some buttons will be hidden. An example of this is the 'Validate' button in the stock.picking form view. It is not :visible but it should still be possible to trigger through scanning a 'O-BTN.validate' barcode. opw-676741 
On smaller screens some buttons will be hidden. An example of this is
the 'Validate' button in the stock.picking form view. It is not :visible
but it should still be possible to trigger through scanning a
'O-BTN.validate' barcode.

opw-676741
[IMP] barcodes: BarcodeEvents uses reserved barcodes prefixes 2015-09-03T09:11:56+00:00 Arthur Maniet arthurmaniet@me.com 2015-09-02T17:45:08+00:00 27e237346d686e6a24e3865cb0877ab1ef43078a Export a list of barcodes prefixes used for software functionss 
Export a list of barcodes prefixes used for software functionss
[ADD] barcodes/web: element button can use attribute barcode_trigger 2015-09-01T11:26:02+00:00 Arthur Maniet arthurmaniet@me.com 2015-08-27T14:29:34+00:00 121556dcea72be9f4829b46a9ca03e00866e7c92 A button can be triggered when a barcode corresponding to its attribute 'barcode_trigger' is scanned 
A button can be triggered when a barcode corresponding to its attribute
'barcode_trigger' is scanned