|
|
| (4 intermediate revisions by one other user not shown) |
| Line 1: |
Line 1: |
|
| |
|
|
| |
| == 17.01.25 Mail threading ==
| |
| Here the very latest mock up of our innovative threading system.
| |
|
| |
| A thread bar next to the message content shows the entire conversation structure (who answer to who) using a different color per email address.
| |
| This system guarantee a great use of space and full control while choosing what message to read.
| |
|
| |
| '''Logic'''
| |
|
| |
| Messages are represented only by the person (avatar, random image, name, or initials of name). We do not show subject, date in this view. Read/unread is shown by visual style.
| |
| Replies are shown using lines connecting the reply to the replied-to message.
| |
| It highlights the currently selected message. Clicking on a node selects that message and allows to read it, and also focuses the graph on that msg.
| |
|
| |
|
| |
| '''Algorithm'''
| |
|
| |
| If a msg is a reply, it's indented one level more to the right, and a short curvy diagonal line joins the line to its left.
| |
| Unless it's the only reply, in which case it's not indented, but directly below the previous message, and has a line straight up.
| |
| Unless (space issue) it has multiple replies and there already is a message to its right, which also has replies.
| |
| Line goes straight down from a message, unless it has no replies.
| |
|
| |
| [[File:Mail_threading.png|thumb|alt=Mail threading|Mail threading]]
| |
|
| |
| [[File:Thread bar.png|thumb|alt=Thread bar|Thread bar]]
| |
|
| |
|
| |
|
| |
| This visual representation offers an intuitive and space-efficient interface, allowing users to quickly understand the structure of the thread and easily navigate between messages. By combining graphical elements such as avatars, connecting lines, and indentation, the system provides a functional and aesthetic way to manage complex conversations.
| |
|
| |
| Feel free to tell us what you think about it!
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
| == 15.01.25 Calendar Edit Dialog ==
| |
|
| |
|
| |
| Current solutions like Microsoft Teams, Thunderbird, and Outlook offer various approaches to display participant availability. However, these often require navigating separate windows or assistants, which can disrupt the event creation flow.
| |
| Integrated Availability View
| |
| To enhance user experience, we propose integrating participant availability directly into the New Event dialog.
| |
|
| |
| This integration would include:
| |
|
| |
| *Availability indicators while typing/searching participant names
| |
|
| |
| *A comprehensive table showing globally all participants' availability with color-coded status indicators:
| |
|
| |
| - All available
| |
| - No information
| |
| - Some available/some not
| |
| - Blocked
| |
|
| |
| *Tooltip functionality on hover, displaying detailed availability information
| |
|
| |
| [[File:Last one.png|thumb]]
| |
|
| |
|
| |
|
| |
|
| |
|
| |
| ''Get Involved?
| |
| - ''Star our GitHub repository to show your support and keep track of updates.
| |
|
| |
| ''Remember, open source is about collaboration and community.''
| |
| ''Every contribution, no matter how small, moves us forward. Let's work together to create a calendar solution that truly serves the needs of our users.When'' ''replying, please stay on topic with feedback about the above content and images provided for improving User Experience (UX). Off-topic ideas and ''suggestions'' can be shared elsewhere at https://connect.mozilla.org/.''
| |
|
| |
|
| |
| Ben
| |