| Age | Commit message (Collapse) | Author |
|---|
|
Planner is like web Tips : a data in a module.
- Rename planner.planner to web.planner
- Rename files according to guidelines
- Remove planner_crm module
- Make CRM depends on web_planner, and add its planner as crm data
- Remove duplicate less style
- Add 'active' boolean field on planner (to disabled them), and create planner backend views
|
|
save planner data when the webclient trigger an action (using core.bus), and fixing the url of CRM planner.
|
|
The module system needs to know the dependencies of a given module
before executing the function. This is why the dependencies were
defined once in an array, and then were described one more times in the
call to require.
But a trick can simplify this: the boot function can parse the string
representation of the module and extract the calls to require from it.
It is more work for the processor, but it leads to simpler module
definitions.
|
|
|
|
- re-enable animation effect when click on "Mark as done" button
- examples for the notepads do appear again when clicking on "?"
- progress bar should be at a few % at first launch of the planner
|
|
|
|
margin-right of the planner launcher to homogenize the icon in the systray
|
|
Add default value because top menu 'Website' from backend don't have a data menu-parent, and toString from undefined displays a traceback.
|
|
(oe_systray)
* Only trigger a menu reflow when needed (show/hide planner)
* Do not include webclient and menu; use webclient reference
(Courtesy of sle-odoo)
Also, change the way to switch planner page. Switching keep now the URL fragment of the webclient, and don't use collapse bootstrap class. Fix url builder server side.
|
|
module. A planner is a tool helping people to set up quickly. For CRM, it helps to define sales strategy, objectives, leads, KPIs and much more !
|
