Daily updates from Odoo
Tuesday, June 4, 2019
3 changes
Enhancements to existing features
Website pages now show sooner by loading most frontend JavaScript after the initial page display instead of blocking it. This improves perceived performance across website, ecommerce, payments, surveys, live chat, tours, and portal pages while adding safeguards for features that still need scripts before interaction.
Original PR description
* web, survey, account, im_livechat, payment, web_tour, website_sale, base Before this PR, the asset bundles were loaded in a synchronous way, so website pages appeared to the user when all the css *and* js were downloaded, parsed and executed. This PR adds a series of improvements to enable lazy loading the JS on the frontend. Especially: 1) Extract the minimum part of the assets common: - promises library and polyfill - boot.js 2) Create "assets_common_lazy" which is "assets_common" - "minimum" 3) Include the "minimum" assets in frontend layouts using "defer" loading and "assets_common_lazy" using "lazy" loading 4) Create a script to do the actual lazy loading in a "minimum" frontend assets 5) Lazy load the current frontend / website editor assets See sub-commits for details. task-1961045
Users can now choose which optional columns appear in list views, making dense screens easier to read while preserving access to extra details. Several sales, accounting, purchasing, repair, HR, and stock-related views were updated to use these optional fields, and choices are saved for future sessions.
Original PR description
Task:https://www.odoo.com/web#id=1902765&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.ab58c2bfb07bc3737628a50b94ab161e -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The forecast app is revamped to make the Gantt calendar the main way to plan work, with easier editing, flexible durations, recurring forecasts, and employee availability visibility. Teams can now use forecasts as practical planning schedules and send plans to employees, improving staffing coordination and forward planning.
Original PR description
This merge revamp the forecast application. It provides some important changes. 1/ First, the gantt view is now primary. It can be use to edit and move forecast. User is not force to have a fix…
This merge revamp the forecast application. It provides some important changes. 1/ First, the gantt view is now primary. It can be use to edit and move forecast. User is not force to have a fix lenght for a forecast, he can create forecast of any duration. Grid view is still used, with an option to set it as first view. 2/ Forecast can now be use as "planning" (forecast assigned with 100% of employee time). Feature to send planning to user are now provided. 3/ Gantt view has been improved and customized for forecast: avatar of employee, grey cells for unavailabilities depending of the group by, no "loop" icon as dates fields are required, ... 4/ Recurrency: a forecast can be recurrent. User might want to assign employee time at regular fixed intervals. You can attach a forecast to a recurrence. Changing the project, the employee or the task will extract this forecast for the recurrence. Technically, we created a dedicated model to handle the recurrency. When creating a forecast throught the wizard, the recurrence and the first forecast are created. Then a subsequence of the recurrency is generated (not all, depending of the "visible period" setting). A cron is scheduled to generate forecast in advance. This completely revamp the forecast application. Future work will come. The goal of this module is to allow users to use forecast as forecasting app and/or planning app. Task-1929079