Odoo/addons/web_planner/static/src/js/web_planner_backend.js, branch 14.0 The current checkout of upstream Odoo [REM] web_planner: Remove the module 2017-10-26T14:14:21+00:00 Yannick Tivisse yti@odoo.com 2017-10-26T11:48:07+00:00 7ed9a7fabeb613bf8b2c2980190399e8f9bbaa2b Purpose ======= User tests have been made by the Product Owners team. It showed that the planners are not used by new users on Odoo due to several reasons (They are too static, too heavy to use,...) Specification ============= Remove the module and its different applications. The onboarding on the business flow will be improvement in the weeks to come. 
Purpose
=======

User tests have been made by the Product Owners team. It showed that the planners are not used by new users on Odoo due to several reasons (They are too static, too heavy to use,...)

Specification
=============

Remove the module and its different applications. The onboarding on the business flow will be improvement in the weeks to come.
[REF] web, *: simplify our RPC system (in JS) 2017-04-11T17:44:38+00:00 Géry Debongnie ged@odoo.com 2017-03-20T14:23:19+00:00 2106e3dd2ecd61096d7c7531c2f18b00fb30aeea The RPC system was not completely satisfactory, we decided to prepare the future and do it properly. This commit introduces the new rpc system, which replace the previous new one. We now simply have a method, this._rpc, which takes a dictionary of parameters. The idea is that depending on the parameters, it is able to add correct default value when necessary. For situations where we don't have the this._rpc method, we can use the rpc.query method, which takes the same arguments, but directly calls ajax.rpc instead of triggering up some events. 
The RPC system was not completely satisfactory, we decided to prepare
the future and do it properly.  This commit introduces the new rpc
system, which replace the previous new one.  We now simply have a
method, this._rpc, which takes a dictionary of parameters.  The idea is
that depending on the parameters, it is able to add correct default
value when necessary.

For situations where we don't have the this._rpc method, we can use the
rpc.query method, which takes the same arguments, but directly calls
ajax.rpc instead of triggering up some events.
[REF] *: use _rpc method for all rpcs 2017-04-11T17:44:38+00:00 Géry Debongnie ged@odoo.com 2017-03-07T15:14:05+00:00 86a87aa8b0dde2237cfe1bb769724e8ed269b62e The _rpc method is now the preferred method to do a rpc, so we need to update all calls. 
The _rpc method is now the preferred method to do a rpc, so we need to
update all calls.
[REF] web,*: remove 'web.model' and 'web.dataModel 2017-04-11T17:44:38+00:00 Géry Debongnie ged@odoo.com 2017-03-05T08:34:56+00:00 e5740270568404d71a3bc093074a085c9c2eded8 Use this.rpc instead of Model object, with web.ajax if necessary. nb: EventDispatcherMixin include now the custom_events managment instead of widget 
Use this.rpc instead of Model object, with web.ajax if necessary.

nb: EventDispatcherMixin include now the custom_events managment instead
of widget
[IMP] web,website: Only display planner for group_system users 2016-12-01T15:32:01+00:00 Kishan Gajjar kig@odoo.com 2016-11-08T05:58:03+00:00 167057800bf015cbed193a34ba8dd45691d110ae Planners should only be visible for "base.group_system" user group (admin settings) because there are links to install apps etc. For now missing access rights messages whenever you click a settings link.Only for admin and not by company. Admin and the user who has "base.group_system" rights can see the planners. 
Planners should only be visible for "base.group_system" user group (admin settings) because there are links to install apps etc. For now missing access rights messages whenever you click a settings link.Only for admin and not by company.
Admin and the user who has "base.group_system" rights can see the planners.
[REF] web_planner, *: refactor planner code 2016-11-15T12:08:59+00:00 qsm-odoo qsm@odoo.com 2016-11-08T17:08:17+00:00 669336baa9b9ef187bd867272761b8299afab6dd * Share code between website and backend * Do not do a [100ms - 500ms] RPC on each app change in the backend but do it only if the planner is asked to be opened * Use the Dialog class so that the planner is not broken * Simplify/optimize code, use standard conventions, lint files, ... 
* Share code between website and backend
* Do not do a [100ms - 500ms] RPC on each app change in the backend
but do it only if the planner is asked to be opened
* Use the Dialog class so that the planner is not broken
* Simplify/optimize code, use standard conventions, lint files, ...
[IMP] mail,web,web_planner: order of systray items 2016-09-28T14:55:51+00:00 Aaron Bohy aab@odoo.com 2016-07-12T13:04:09+00:00 66cb0d7aa3d286f3d57a7a675fd7102406dc82a5 Sort systray items by sequence to allow, e.g. to force the planner item to be the left-most item of the systray as it is not displayed in all apps, and thus produces a flickering of the other items. Also invert the push order of the two mail items to keep the previous order as they are now prepended instead of appended. 
Sort systray items by sequence to allow, e.g. to force the planner item to
be the left-most item of the systray as it is not displayed in all apps, and
thus produces a flickering of the other items.

Also invert the push order of the two mail items to keep the previous order
as they are now prepended instead of appended.
[FIX] web_planner: hidden by default 2016-01-08T14:57:21+00:00 Géry Debongnie ged@odoo.com 2016-01-08T14:34:22+00:00 0336f109f18330e986531f672d00d69cc058839b The web planner should be hidden by default. Now, it is displayed, then hidden in js after a while (but it can be seen by the user), then displayed again if necessary 
The web planner should be hidden by default.  Now, it is displayed,
then hidden in js after a while (but it can be seen by the user), then
displayed again if necessary
[IMP] web(_planner),website: navbars & menus merge 2015-12-24T16:11:55+00:00 qsm-odoo qsm@odoo.com 2015-12-22T14:32:04+00:00 bcca4a44c79d94db320ffe6f8311fcbb7ff81421 Merge appswitcher navbar and app navbar. Merge planner menu and user menu. 
Merge appswitcher navbar and app navbar.
Merge planner menu and user menu.
[FIX] website, web_planner: shared help comportement in frontend/backend 2015-09-28T13:42:44+00:00 Martin Geubelle mge@odoo.com 2015-09-25T11:48:39+00:00 5946623d3fdcb2bbb914fc3ab4e005b462c74aea Help has been moved to web_planner, but only in backend. The comportement needs to be defined in website also so it is now shared in frontend and backend (mixin in common) 
Help has been moved to web_planner, but only in backend. The comportement needs to be defined in website also so it is now shared in frontend and backend (mixin in common)