Skip to content
This repository has been archived by the owner on Aug 13, 2018. It is now read-only.

Proposal for the arrows indicating whether the message comes from the Client or the Server #17

Open
fflorent opened this issue Oct 14, 2015 · 2 comments

Comments

@fflorent
Copy link
Member

Currently, there is an arrow that indicates the origin of a message (the client or the server). Here is a message coming from the server :
selection_054

What about making an arrow going downward for a message coming from the server, and an arrow going upward for a message going to the latter ? That would be similar to what we can see with the download / upload icons.

What do you think?

Florent

@janodvarko
Copy link
Member

The UI/UX concept we've been using for displaying the list of frames (and also RDP packets in the RDP Inspector) is based on 'user-chat-ui'. Chat UIs (like What'sApp, Skype, etc.) are displaying incoming messages on the left and sent messages on the right.
We used the same approach in the list-view perspective: received frames on the left and sent frames on the right. To be inline with the idea, we are also using arrows in the table perspective: received frames points to the left, sent frames points to the right.
So, I rather disagree with changing the direction.
But we can definitely change the visual aspect of the icons so, they are more similar to the arrows used in the list view!
Honza

@fflorent
Copy link
Member Author

The UI/UX concept we've been using for displaying the list of frames (and also RDP packets in the RDP Inspector) is based on 'user-chat-ui'. Chat UIs (like What'sApp, Skype, etc.) are displaying incoming messages on the left and sent messages on the right.

In the chat UIs, the context is a bit different. The users know what they type, so it's quite natural to determine what message is incoming / outgoing.

In this particular context, the user inspects the outgoing messages as well as the incoming ones, so they might not know what are the outgoing messages.

Maybe we could wait for feedback on this issue.

Florent

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

No branches or pull requests

2 participants