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
* Tip are never destroyed when change view mode * unbind methods * mail: memory leak with unbind methods * web: memory leak because 'ui-autocomplete' is never destroyed * web_editor: memory leak for wrong unbind on destroy * web: memory leak: must remove fileupload handler * bus: memory leak: correctly debind handlers on window in bus.Bus * remove handlers on switch buttons and views $buttons * remove handlers on breadcrumbs * web: memory leak: correctly debind handlers * im_odoo_support: memory leak: remove fileupload handler odoo_support Note: part of this commit was actually authored by aab
When you browse through the views of an action and then hit the back button, the view does not change. For example, go to the customers kanban, click on a customer, hit back, you're still in the customer form view. related rev: 46857d267b46c6ae91817231f8293403117bb75e `do_load_state` is called when you hit f5 or press the back button on your browser. The related rev took care of fixing the ugly part that make the webclient goes trough the multi record view then the mono record view when you hit f5 on a mono record view. In this context, it removed the code in view manager's `do_load_state` that switched the mode of the action if it isn't the same the one the web client is trying to restore from the state (because now the correct mode is loaded). However, if you hit the back button while the previous view is in the same action, it obviously doesn't switch the mode anymore and you're facing the same view. The issue is fixed by restoring the switch_mode in the view manager's `do_load_state` (without its oudated comment).
The view `sale_team_dashboard` (which extends kanban) has been removed and replaced by a default kanban view. To use it in the ViewManager, an option `js_class` is added on the arch description and this class be used as the View. This avoids creating a new view type just for one view.
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
Introduction of 'data_manager' service which handles meta-data related to actions and views (fields_views, fields and filters). Ideally, all RPCs to get that kind of information should go through data_manager, as it holds an internal cache.