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

Generate 1-2 new streamlined UI options for filmstrip view #92

Closed
bnmajor opened this issue Feb 15, 2024 · 4 comments
Closed

Generate 1-2 new streamlined UI options for filmstrip view #92

bnmajor opened this issue Feb 15, 2024 · 4 comments

Comments

@bnmajor
Copy link
Collaborator

bnmajor commented Feb 15, 2024

The "agree" radio buttons are not needed. We should investigate better ways to handle approving/changing/skipping a prediction.

May be related to #64

@bnmajor
Copy link
Collaborator Author

bnmajor commented Feb 19, 2024

@cooperlab @jagstein @manthey @jeffbaumes

I have a few ideas for dropping the "agree - yes / no" radio buttons. The common traits across all are:

  1. The drop-down menu is always shown
  2. The drop-down menu now has a No Selection choice (or some variation of that wording) which is the equivalent of resetting the selection.
  3. If the user agrees with the prediction the selection text is emphasized in some way.

Some additional options:

  1. "Agree" alternatives
    1. We can replace the radio buttons with a checkbox. Checking the box automatically selects the label matching the prediction from the drop-down menu (and applies any text emphasis we decide is appropriate).
    2. We can remove the radio button but not add the checkbox. The user will have to use a hotkey or the drop-down menu to select the class.
  2. Text emphasis
    1. Italicize the No Selection option to emphasize that no choice has been made.
    2. Bold the selection when it matches the prediction
    3. Color and thicken the selector border once a user has made a selection - red for "disagree", green for "agree"

Examples:

  1. Image
  2. Image
  3. Image

Any combination of ideas would be fine of course. My personal preference is for example number 3, with the option of including the checkbox if users are not using hotkeys and want a faster way to agree with predictions. The checkbox could also be moved below the drop-down menu if it seems useful to keep but less likely to be used than the menu.

@jeffbaumes
Copy link

I like the idea of not having the checkbox, so choices 2 or 3. IMO since we are using colors for category on the main view, we shouldn't try to also use color to indicate matching prediction. So I have a slight preference for option 2 but we should get input from Jeff G.

@jagstein
Copy link

jagstein commented Feb 19, 2024 via email

@bnmajor bnmajor mentioned this issue Feb 27, 2024
@bnmajor
Copy link
Collaborator Author

bnmajor commented Mar 1, 2024

Closing as completed in #99

@bnmajor bnmajor closed this as completed Mar 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

3 participants