Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow toggle between default view and conversation view #395

Closed
progandy opened this issue Aug 25, 2011 · 4 comments
Closed

Allow toggle between default view and conversation view #395

progandy opened this issue Aug 25, 2011 · 4 comments

Comments

@progandy
Copy link

I'd like to have a hoktey and a button on each message in conversation view that allows me to toggle between the default message display and the conversation view. This will be very helpful while there are still actions and information in the default view which is not displayed in the conversation view. (eg return receipt requests, toolbar buttons, etc)

@protz
Copy link
Collaborator

protz commented Aug 25, 2011

Hi,

While this is an often-requested feature, it is likely not to be implemented. This would make things extremely complicated, and the goal of Thunderbird Conversations is to provide a suitable alternative to the message reader. I'd rather have you explain why you still have to go back and forth rather than provide you with a way to disable, even temporarily, the conversation view.

Return receipts won't be implemented in the near future, although this is an easy bug, so you're welcome to tackle it. I could provide directions if you're interested. Toolbar buttons already provide a lot of functionality. What is it you're missing exactly?

@protz protz closed this as completed Aug 25, 2011
@progandy
Copy link
Author

progandy commented Sep 4, 2011

The toolbar buttons aren't too important, I just thought the keyword-button would be nice to have to quickly tag a single message and not the whole conversation.
The problem are the return receipts since I dislike it when they are sent automatically and I need the confirmation button which is not available and there isn't any indication of a requestet notification. If I find some free time I'll have a look at it.

@alexrah
Copy link

alexrah commented Dec 13, 2015

hi,
I'd like to have directions on how to implement the "return receipt" button in conversation view.
Thanks!

@protz
Copy link
Collaborator

protz commented Dec 14, 2015

Hi there,

See #129 for
some thoughts; basically, you would need to re-implement the logic from
http://mxr.mozilla.org/comm-central/source/mail/base/content/mailWindowOverlay.js#3070
that detects whether the message wants a return receipt or not.

There are two codepaths: for messages that are streamed
(MessageFromDbHdr), you just need to read the various headers after you
get the MimeMsg. For messages that come from Gloda, you can implement a
Gloda plugin at indexation-time (there are examples of that in the
source) that flags each gloda message with a property that says whether
the sender wants a return receipt.

Then, you need to re-implement the logic for sending the status delivery

notification. You need to imitate:

http://mxr.mozilla.org/comm-central/source/mailnews/extensions/mdn/src/nsMsgMdnGenerator.cpp#1052
(to make sure that when the user views the message with the classic
reader, they're not prompted to send it again)

  • then you need to use modules/stdlib/send.js to send the delivery
    status notification (just re-implement the regular text that Thunderbird
    uses)

Feel free to ask for more guidance on
#129!

Cheers,

Jonathan

The steps would be as follows:

  • in modules/message.js, modify MessageFromDbHdr

~ jonathan

On 12/13/2015 03:36 PM, alexrah wrote:

hi,
I'd like to have directions on how to implement the "return receipt"
button in conversation view.
Thanks!


Reply to this email directly or view it on GitHub
#395 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants