* web_editor, web_planner, website The 'Dialog' class is used in both backend and frontend. Also, lots of actions can be done without the use of any modal. It thus makes sense to lazy load its related xml only when a first modal is opened. This change also allows to get rid of the "base_common.xml" file as the dialog template is the only remaining one in there and, in the future website update, it will allow to not load any static XML file on website page loadings.
Qweb rendering is great to render "complex" widget structures. However, using it to render something as simple as a button was not very meaningful. This commit deletes the "WidgetButton" template and replaces it with an utility JS function to render buttons according to given parameters. Also, this change will allow a better change. Before this commit, the only templates left in the "base_common.xml" file are the "WidgetButton" and the "Dialog" ones. With the removal of "WidgetButton", the file can now be lazy loaded only if necessary, on the first dialog instantiation. This will allow to remove the need to load static XML files on each frontend page loading.
WidgetLabel.tooltip and WidgetButton.tooltip are backend static xml templates. They should never have been in base_common.xml.
Since commit https://github.com/odoo/odoo/commit/09659cca30a98dd9a522c53918e389e0d8f667eb: The switch company menu feature has been introduced, which is a backend one. The associated static XML was placed in the common xml file by mistake.
The user menu was not visible in portrait mode with multi company in mobile. This was caused by the company menu taking too much room. We fix the issue by making the company menu smaller (just the size of an icon) (PR #16685, task 29394)
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
When a modal was opened, the system seemed slower because a web_tour callback was called every 500 ms. This was because of jQuery. Using the "find" method on a jQuery element will temporary set an ID on this element for some jQuery reason. So, when a modal opened, a DOM mutation was caught by the web_tour observer which then called the "update" method in which a $modal.find is done... and so an ID was set and a new DOM mutation was caught again. The solution here is to provide an unique ID on each modal in odoo so that the find function has not to set an ID, and so does not trigger any DOM mutation.
Avoid duplicating web addon in enterprise by extracting a common basis. Enterprise features stay in enterprise, but use that common basis. Mainly: - JS refactoring and linting - Conversion of .sass into .less split into multiple files - Templates cleaning and DOM simplification - Re-generation of web.pot, and update of .po files
If the user has multicompany rights and more than one allowed companies, the full company name is displayed in the topbar. When you click on it, there is a dropdown with the name of the other companies. Clicking on another company name makes you switch on it and reload the page