Odoo/addons/mail/static/src/xml/mail_chatter.xml, branch 14.0 The current checkout of upstream Odoo [REF] mail: last part of the chat refactoring (client side) 2015-10-01T12:00:18+00:00 Géry Debongnie ged@odoo.com 2015-09-30T12:14:30+00:00 2a5f07e0b919d4209c2cb72c6dfdc8b86cd5c7ff Removal of old files and update of assets and imports Joint work with aab 
Removal of old files and update of assets and imports

Joint work with aab
[FIX] mail : suggested partner check on chatter composer. 2015-09-18T09:50:40+00:00 Jérome Maes jem@openerp.com 2015-09-17T12:04:45+00:00 ba0d2060f8af1af7076fbe51858f424e828fb5b4 Embedded the template core in a 'root widget tag' to make the selector 'this.$('.o_mail_chatter_compose_message_suggested_partners input:checked')' works. 
Embedded the template core in a 'root widget tag' to make the selector 'this.$('.o_mail_chatter_compose_message_suggested_partners input:checked')'  works.
[IMP] mail: load more messages: scrolling 2015-09-01T19:04:34+00:00 Aaron Bohy aab@odoo.com 2015-09-01T08:54:15+00:00 c2f2a518313727b090831da30a20add775c6970c - In the chat, when loading more messages, automatically scroll to the previous oldest message instead of staying at the top; - In the chat, don't use the event 'scrollTop < 50' to load more messages as it won't work on mobile (all the webclient is scrolling, so the client action's scrollTop will always be 0); - Generalize the way to load more messages between chat and chatter by moving the logic to the MailThreadMixin and creating a common template; - Improve the style of this 'load more messages' button 
- In the chat, when loading more messages, automatically scroll to the previous
oldest message instead of staying at the top;
- In the chat, don't use the event 'scrollTop < 50' to load more messages as
it won't work on mobile (all the webclient is scrolling, so the client action's
scrollTop will always be 0);
- Generalize the way to load more messages between chat and chatter by moving
the logic to the MailThreadMixin and creating a common template;
- Improve the style of this 'load more messages' button
[REF] mail: chatter 2015-09-01T19:04:29+00:00 Aaron Bohy aab@odoo.com 2015-08-27T12:38:19+00:00 0d7083f76632cd284dee52aca9c23a6e424f1930 DOM and LESS simplification New design integration 
DOM and LESS simplification
New design integration
[REF] mail : include real time, and replace Timeline features 2015-09-01T18:16:09+00:00 Jérome Maes jem@openerp.com 2015-08-11T08:17:10+00:00 449f25463843767ba41a9a8c2adfdd4ceb2f2e5c This commit add instant messaging features in mail module to make it a real team collaboration tool. Lots of these new features will replace Timeleine view (which is not removed in this commit). Many files have been moved, split or created for a better structure. - My Channels : A user can be member of channel (mail.channel). These are discussion group, but also an aggregate of notification. Setting a channel as document follower, it will receive all the message (of the chatter) in real time, as information stream. - A new Inbox : this aims to replace the timeline view. The user will see its channels grouped by 'slot', and receive the message in real time. Jump to the form view, invite people, create private discussion group, talk directly to another employee, ... are the main features. Your message can still be starred. The 'Inbox' will only contain your needaction. - Needaction concept : a needaction is a message calling you to do something. If you follow a document as a person, the posted message will be 'needaction' for you. It can also be a message where you are mention with a '@my_name' (this feature is not added in this commit). - The chatter doesn't change so much. It still allow you to see the discussion about the document, to star some message, and treat your needaction. - Chat : the only way to have a minified conversation is from the Inbox Client Action. It allow you to keep an eye on a channel when working on document. - Compose Message : it is now common to the Inbox, and the chatter. It offers shortcode substitution, attachments management, and optional subtype. - UI : the chat window has been clean, they have a new look now. To do so, - Chatter code have been completely rewrite, independently of timeline view - Add 'bus' as mail dependency, to insure real time - A mail.message is broadcasted on the bus channel (db, mail.channel, channel_id), and a channel header on (db, res.partner, partner_id) - Extracting mail_thread mixin used for Chatter and ChatMailThread (Inbox client action). This uniformize the programming structure with the server side - Clean CSS style and use LESS instead of CSS - Define a new messafe format (message_format method in mail_message.py), compatible with fetching and broadcasting - Apply guideline coding conventions This commit also break the module im_livechat, since im_chat models don't exists anymore and will be fixed in the next commit. Thanks to Thibault Delavallee (tde) for the long debates and precious advices, Richard Mathot (rim) for the support, Simon Lejeune (sle) for the client action layout, and the Usability Team (apr, lle, bst yti) for the long testing. Conflicts: addons/mail/models/mail_thread.py 
This commit add instant messaging features in mail module to make it a real team collaboration tool. Lots of these new features will replace Timeleine view (which is not removed in this commit). Many files have been moved, split or created for a better structure.

- My Channels : A user can be member of channel (mail.channel). These are discussion group, but also an aggregate of notification. Setting a channel as document follower, it will receive all the message (of the chatter) in real time, as information stream.

- A new Inbox : this aims to replace the timeline view. The user will see its channels grouped by 'slot', and receive the message in real time. Jump to the form view, invite people, create private discussion group, talk directly to another employee, ... are the main features. Your message can still be starred. The 'Inbox' will only contain your needaction.

- Needaction concept : a needaction is a message calling you to do something. If you follow a document as a person, the posted message will be 'needaction' for you. It can also be a message where you are mention with a '@my_name' (this feature is not added in this commit).

- The chatter doesn't change so much. It still allow you to see the discussion about the document, to star some message, and treat your needaction.

- Chat : the only way to have a minified conversation is from the Inbox Client Action. It allow you to keep an eye on a channel when working on document.

- Compose Message : it is now common to the Inbox, and the chatter. It offers shortcode substitution, attachments management, and optional subtype.

- UI : the chat window has been clean, they have a new look now.

To do so,
- Chatter code have been completely rewrite, independently of timeline view
- Add 'bus' as mail dependency, to insure real time
- A mail.message is broadcasted on the bus channel (db, mail.channel, channel_id), and a channel header on (db, res.partner, partner_id)
- Extracting mail_thread mixin used for Chatter and ChatMailThread (Inbox client action). This uniformize the programming structure with the server side
- Clean CSS style and use LESS instead of CSS
- Define a new messafe format (message_format method in mail_message.py), compatible with fetching and broadcasting
- Apply guideline coding conventions

This commit also break the module im_livechat, since im_chat models don't exists anymore and will be fixed in the next commit.

Thanks to Thibault Delavallee (tde) for the long debates and precious advices, Richard Mathot (rim) for the support, Simon Lejeune (sle) for the client action layout, and the Usability Team (apr, lle, bst yti) for the long testing.

Conflicts:
	addons/mail/models/mail_thread.py