This commit is a significant rewriting of client-side discuss, chatter, chat window, and messaging menu using OWL. The behavior should be broadly the same, with some slight functional changes here and there. From a technical standpoint, the code of messaging is mainly organized in 2 main groups of modules: - models, which are logical entities that depict the client-side state of messaging as a whole. - components, which are in charge of displaying information from models. This refactoring also introduces new JS guidelines regarding folder structure (/static) and naming rules for JS modules. Community PR: https://github.com/odoo/odoo/pull/39023 Enterprise PR: https://github.com/odoo/enterprise/pull/6249 Task-1914207 This PR is a collaborative work by Alexandre, Julien, Sébastien and Xavier, with the precious help of Lucas to speed it up towards the end. closes odoo/odoo#39023 Related: odoo/enterprise#6249 Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com> Co-authored-by: Alexandre Kühn <aku@odoo.com> Co-authored-by: Julien Giannone <jgi@odoo.com> Co-authored-by: Lucas Perais <lpe@odoo.com> Co-authored-by: Sébastien Theys <seb@odoo.com> Co-authored-by: Xavier Dubuc <xdu@odoo.com>
closes odoo/odoo#52826 Related: odoo/enterprise#11084 Signed-off-by: Aaron Bohy (aab) <aab@odoo.com>
In fb051d3420 there was some changes on drag and drop of chatter windows, but this would break the drag and drop of summernote because it wait for document.drop event for hiding the drop zone. opw-2259522 closes #51448 closes odoo/odoo#51478 X-original-commit: 4aaf5b1f562f4cd30e05b020741eb936f6e20a20 Signed-off-by: Nicolas Lempereur (nle) <nle@odoo.com>
Before this commit, when "Send message" composer was open with some suggested recipients, and then editing and saving data related to the suggested recipients, the suggested recipients were not updated on composer until some user interactions like page reload. Steps to reproduce: - Open an opportunity in CRM; - Open "Send message" composer; - Change "Email" field; - Save changes; > Suggested recipient above composer textarea is not updated with newly saved email adress. It becomes updated only after some user interactions, such as toggle "Log note" then "Send message" or with a page reload. This commit fixes the issue by updating the suggested recipients on the composer in real-time when clicking on "Save". Task-Id 2089816 closes odoo/odoo#40033 Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com> Co-authored-by: Mohammed Shekha <msh@odoo.com> Co-authored-by: Alexandre Kühn <aku@odoo.com>
This reverts commit e5479fcfdb76bdbf9301fb140d873483bafdb9e4. This commit prevented an issue of losing messages on post in case of connectivity loss. The implementation consists of keeping the content in the composer until the server acknowledges handling the message. However, this solution introduces significant issues. For instance, sending messages in quick succession will likely loose or duplicate some content, based on how fast/slow the RPC `message_post` is resolved. Plus, there was an issue on mobile because the input focus was lost during the RPC. As a consequence, the virtual keyboard flickered. The intent was to fix a rare issue, and since the problems of this solution clearly outweigh the gain, we decided to revert. closes odoo/odoo#41544 X-original-commit: 36b2e99e08bfc6d92a821d0346e783695580abf9 Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com>
PURPOSE Clean posting process and improve mail.message definition and comprehension. SPECIFICATIONS In order to be more explicit subtype parameter is renamed to subtype_xmlid. It therefore clearly indicates it should be a valid subtype Xml ID. Support of ill formatted Xml IDs is removed because there is no reason to try to add some random prefix. Give something that exists or go to hell, punk ! LINKS Task ID 2071556 PR #38692
There are too many image sizes. Since they are stored resized this takes time to generate when saving a new image, it's more rows on the attachment table, more files on the disk, ... 64px is close enough to 128px that it can be removed without a big impact on download size. It will even reduce download and number of requests when both images are displayed because now only one has to be downloaded and then benefit from cache. The difference between the two is typically around 1.5kB which is negligible these days, especially when the request overhead is around 0.5kB already, not even taking into account other factors such as latency. If a 64px image must absolutely be returned, it is still possible to pass the size parameters to the image route. But the current guideline is to handle resizing in the views when necessary. Views ===== - remove width and height attributes when existing CSS rules are overriding them (eg. `.oe_kanban_avatar` in the right context) - add CSS rules instead of width and height attributes when possible - use `object-fit: cover;` where width and height are forced to avoid distortion of non-square images - for products, use `object-fit: contain;` instead, keep ratio but without crop - add new CSS rules where the expected size was max 64px*64px before due to the image size itself - remove `img-fluid` where using size classes to avoid conflicting rules task-2060865 closes odoo/odoo#36147 Signed-off-by: Sébastien Theys (seb) <seb@odoo.com>
In the chatter composer, suggested partners were shown more than necessary. 1. Create a new partner; 2. Open the chatter composer to send a message (the new partner is suggested as a recipient); 3. Re-open the chatter composer => the partner is still suggested, but it is already a follower now! Task-Id 2050102 closes odoo/odoo#35604 Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com> Co-authored-by: jbm-odoo <jbm@odoo.com>
image_original => image_1920 (now resized to 1920) image_big => image_1024 image_large => image_256 image_medium => image_128 image_small => image_64 image replaced by image_1920 (when writing) or by image_1024 (when displaying what was previously the big size) + add new intermediate format: image_512 PR: #34925
closes odoo/odoo#34850 Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>