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

Set up some rules on when to go for a "radio" or a dropdown menu #132

Open
Remi-Gau opened this issue Jun 29, 2020 · 2 comments
Open

Set up some rules on when to go for a "radio" or a dropdown menu #132

Remi-Gau opened this issue Jun 29, 2020 · 2 comments

Comments

@Remi-Gau
Copy link
Owner

Remi-Gau commented Jun 29, 2020

  • "radio" are quicker but do not offer the possibility of creating of an "Other" reponse field
  • Dropdown make more sense when there are many options
@satra
Copy link

satra commented Jun 30, 2020

agree with the sentiments here.

how about: radio when "other" is not an option and number of items < 7 (magic number for now, presumably re-configurable in the future).

@Remi-Gau
Copy link
Owner Author

Oh yeah totally!

I think the reason I kept it that way for PET-app is that some of the list of items in the original table I converted had a lot of "..." and "etc" so I wanted to have the option of having more response options provided by the "users".

Actually one of the thing to ask Melanie and Martin: provide some more complete lists of response choices.

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

No branches or pull requests

2 participants