linuxmint / linuxmint/warpinator

UI Improvements

Open
#170 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
1.6k
Forks
115
PR merge metrics
No merged PRs in 30d

Description

Hi team, following are some places where UI can be improved to make things more intuitive

Case 1

When waiting for some action for a peer device
image

The clock icon could have a yellow color background like the below one so that it is more easily visible/noticeable to the eye
image

Case 2

When waiting for file acceptance - we can use blue background for the ✓ tick button as it is the preferred action
image

Case 3

Change A

When waiting for file acceptance and files would be overwritten - we can use red background for the ✓ tick button as it is a destructive and generally the preferred action
image

Change B

I think it would be nice to have Files may be overwritten message also in red to indicate that it is talking about a destructive thing and the color would also make it more noticeable (which is required since the transfer is blocked and waiting for the user to make a decision).
image

Case 4

Change A

image
If we observe the above image, generally the preferred action is on the left and the secondary action is on the right. To maintain that consistency, can we have the icons shown in the below case be switched (i.e. left should be open the containing folder, right should be remove this operation from the list). This change will also ensure that remove this operation from the list icon is always on the right hand side
image

Change B

Since open the containing folder is the preferred action, but not an action where warpinator is waiting for the user to approve file receiving/sending, we can have a light blue background (instead of a bright blue which is used in case 2 above) for the button

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the four screenshot-backed UI cases and trace the corresponding waiting, acceptance, overwrite-warning, and completed-operation states in the interface. Confirm the existing action order and color conventions before changing them. Done means all requested icon ordering, button backgrounds, and overwrite-warning emphasis are applied consistently across these states.

Written by the indexing model from the issue text.

Assessment

Domain
design, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.