Jump to content

Editing Talk:Main Page

Add topic
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:


== 17.01.25  Mail threading ==             
Here the very latest mock up of our threading system.
A thread bar that shows the entire conversation structure (who answer to who) using a different color per email address.
This system garantee a great use of space and full control while choosing what message to read. You can even start each individual part of the thread.
'''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.
'''Placement'''
We have a vertical and horizontal version (for desktop and mobile, respectively)
It is shown between message list and message.
It should be narrow (or small, respectively). If there are too many responses, deeper replies are grouped using a "+20" (number of msgs not showing) next to the bottom-most or right-most message.
'''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 threading1.png|thumb|alt=Mail threading|Mail threading]]
== 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.
- ''Participate in our weekly community calls to discuss project direction and ongoing work.''
''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/.''
''If you are a Beta User, comments as such "I am having trouble with X or a question about Y" should be posted at https://support.mozilla.org/questions/new/''thunderbird.''''''''
== 2025-01-14 Are comments possible? ==
I would like to know whether I am allowed to leave a comment about the work, if I have feedback
Ben
Please note that all contributions to UX Parula may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see UX Parula:Copyrights for details). Do not submit copyrighted work without permission!
Cancel Editing help (opens in new window)