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

CSV importer: confusing behaviour of checkboxes #4299

Closed
wetneb opened this issue Nov 15, 2021 · 8 comments · Fixed by #4528
Closed

CSV importer: confusing behaviour of checkboxes #4299

wetneb opened this issue Nov 15, 2021 · 8 comments · Fixed by #4528
Labels
Module: Frontend These issues involve working on HTML, CSS, and JavaScript code that affects the user interface. Type: Bug Issues related to software defects or unexpected behavior, which require resolution.
Milestone

Comments

@wetneb
Copy link
Sponsor Member

wetneb commented Nov 15, 2021

In the configuration options for the CSV/TSV importer, two checkboxes are linked as if one of them had to be checked.

This is a bad pattern: if those checkboxes are really meant to be grouped, then they should be radio buttons and be positioned next to each other.

To Reproduce

Steps to reproduce the behavior:

  1. First, open a CSV/TSV file
  2. Then, click on the "Parse next 1 lines as column headers"

Current Results

import_options

Expected Behavior

In this case I was actually trying to get both checkboxes to be not checked (so that my project gets created with Column 1, Column 2… as column headers). I can achieve this by keeping the Parse next… checkbox on and setting the number of lines to 0 but that is a bit counter-intuitive.

Versions

  • Operating System: Debian
  • Browser Version: Firefox
  • JRE or JDK Version: 11
  • OpenRefine: master (3.6 SNAPSHOT)
@wetneb wetneb added Type: Bug Issues related to software defects or unexpected behavior, which require resolution. Module: Frontend These issues involve working on HTML, CSS, and JavaScript code that affects the user interface. labels Nov 15, 2021
@rachittiwari8562
Copy link
Contributor

I have tweaked the ui a little bit . Does it look fine?
Screenshot from 2022-02-13 12-50-17

@rachittiwari8562
Copy link
Contributor

I think both of the options should be connected as when the user is trying to enter the column names himself , then the parse next checkbox should be turned off .

@wetneb
Copy link
Sponsor Member Author

wetneb commented Feb 13, 2022

I absolutely love it!

@thadguidry
Copy link
Member

Maybe the Use character could be moved above the Trim ?

@rachittiwari8562
Copy link
Contributor

Screenshot from 2022-02-13 22-51-04

Does this fulfil the requirement...?

@rachittiwari8562
Copy link
Contributor

rachittiwari8562 commented Feb 14, 2022

In addiion to this I have tried to add some visual seperation between the 3sections .
Screenshot from 2022-02-14 19-44-36

Should I move forward with this design or revert back to previous one..

@thadguidry
Copy link
Member

@rachittiwari8562 The visual separation is optional and we don't have that in the other import loaders so I would remove those vertical section separators here in the CSV importer for now. Then I think we can merge. There are many many things that visually I would like to see changed and restyled throughout OpenRefine, but first we need a comprehensive plan and that will likely come after or along with OpenRefine 4.0 in phases.

@rachittiwari8562
Copy link
Contributor

Got it...

rachittiwari8562 added a commit to rachittiwari8562/OpenRefine that referenced this issue Feb 14, 2022
wetneb pushed a commit that referenced this issue Feb 15, 2022
@wetneb wetneb added this to the 3.6 milestone Feb 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Module: Frontend These issues involve working on HTML, CSS, and JavaScript code that affects the user interface. Type: Bug Issues related to software defects or unexpected behavior, which require resolution.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants