The hightlight element when a tip is clicked was placed over a white
rectangle. This induced a problem if the element was itself white.
Also the dimension of the helper were badly computed.
+ remove specific tip style in kanban view
Now that most refactoring has been merged
It is better to have red a great work of another culture in translation than never to have read it at all.
― Henry Gratton Doyle
- Add a 'Quotations' button on the sales team kanban dashboard
- Add default stages for crm.lead objects
- Add a pivot view for the opportunities
- Modify a menutip
- Add a few tips
- Preserved explicit 3rd-party copyright notices
- Explicit boilerplate should not be necessary - copyright law applies
automatically in all countries thanks to Berne Convention + WTO rules,
and a reference to the applicable license is clear enough.
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.
* Override message_fetch from mail.Thread in a dedicated limk module (mail_tip)
and fire an event when the messages are loaded. This is necessary for tips on
the chatter.
* Override render_value form web.form.FieldStatus: Call reposition() when a
FieldStatus object is done rendering.
* Tip.reposition() method
* Handle web bus resize event
This commit allows a tip to be properly displayed on elements containing
an img tag. Previously the tip would be displayed before the image could
be loaded, thus breaking the ui.
Yannick Tivisse