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

Upside down thread #160

Open
thisisbenwoo opened this issue May 22, 2023 · 8 comments
Open

Upside down thread #160

thisisbenwoo opened this issue May 22, 2023 · 8 comments
Labels
enhancement New feature or request Funding needed

Comments

@thisisbenwoo
Copy link

Hi All,

I've been trying all sort of things, as well as various extensions. If you take a look at the following:
image

You can see that the latest email in the thread is on the bottom of the thread. I still want everything sorted by the date descending, but for threads, I'd like to see the latest email at the top (this is similar to Outlook I believe), this way, I prioritize the latest in the thread and can probably collapse the thread to be able to fit more emails in the pane.

Is this something that be done in Betterbird? Or is this part of an extension? Or is this not a capability that is available at this time?

If it is not available, could I ask that this be an enhancement for the future please?

Many thanks.

b

@Betterbird
Copy link
Owner

With threaded display, the last received messages gets inserted into the thread tree at the appropriate location, an many cases at the end, or somewhere in the middle. That's a disadvantage of the threaded view. But how else could it be done in a hierarchical tree? Can you send a mock-up as a suggestion?

@thisisbenwoo
Copy link
Author

So here is a very rough mock up. You'll see that the latest message (just for each thread) is at the top, not the bottom. This means that is should show up first when you're looking at the unread messages. Hopes this helps
image

@Betterbird
Copy link
Owner

Sorry, we can't make sense of your mock-up. We've prepared this drawing:
thread

The numbers are the order received or date. On the top left you have the original view. On the right hand side you can see a few options: At the top, the replies are indented to the left but the reverse-date order is applied. The second from the top is mirrored, both boxes and lines. On the bottom image only the boxes are mirrored. You can see that it doesn't work well with the connection lines.

@thisisbenwoo
Copy link
Author

The upside down ones is what I'm looking at. The idea is that the most recent message in the thread is on top. Currently, if the thread is collapsed, (at least in the Unified View), I can't actually see that there is a new message. Doing it this way, new messages relating to the thread will appear on top. It also follows logically because when you reply to each message, the quoted message follows

I hope this makes it clearer. Thanks.

@Betterbird
Copy link
Owner

Betterbird commented May 22, 2023

We've understood your idea. It's annoying to look for new messages at the end of a long thread.

But the graphical reversal (let alone the implementation) isn't straight forward. So did you look at the three proposals on the right? (Looks like the collapse arrow should go to the top.) Looking at your mock-up again, maybe you meant the top right solution.
thread2

@thisisbenwoo
Copy link
Author

That's a great solution, and consistent with the current implementation. Thanks for considering my suggestion.

@Betterbird Betterbird added enhancement New feature or request Funding needed labels May 23, 2023
@Betterbird
Copy link
Owner

This won't happen right now, we're preparing for version 115 to be released in the summer. But we keep the request on file.

@thisisbenwoo
Copy link
Author

Oh please, no rush. I just thought this would be something others and I would find useful as well. Thanks for considering this request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Funding needed
Projects
None yet
Development

No branches or pull requests

2 participants