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
Possibility to adjust column width manually #4806
Comments
Hi @lozanaross , @wetneb , could you assign this issue to me, please? |
Iterating on this issue of letting users control and resize column width, here areat 2 (two) alternative solutions that can both work together or separately. They are:
in my iteration, when a user extends the width of a column, it causes the data contained to spread in order to adjust to the column width. Likewise, when column width is shortened, the data contained therefore, breaks into more lines to fit into the shortened column , which in turn elongates the height of each column and row. The above are shown in these screenshots:
This alternative proposition, which can also work alongside the dragging option ,adds the option to resize columns to the edit column options available to OpenRefine users and just below the option to remove a column. On click, the user is shown a modal to add their desired column width and save and on save, the width added is automatically applied on the column the user chose to resize. This alternative is further explained in the below screenshots; Here's a link to fidn all screenshot designs : |
@Lydiaofficial is it a click, hold button, drag? holding mouse buttons is sometimes cumbersome for folks. It's a small accessibility issue in some regards. Would be nice to avoid having to hold down the mouse button. A click, drag around until you like it, then click again to release... would be my preferred choice if that's possible. Or some other alternative. |
@thadguidry I understand the accessibility issue that holding mouse buttons can cause , so rather, it is a click and drag. The idea is that when users hover on the column lines on the left or right, the drag icon appears and they can click and drag and then click to release. So yes, it is a "click and drag until you like it and click to release " and definitely is possible. |
@Lydiaofficial @wetneb I'm not sure this issue is so appropriate for the Outreachy group. My advice here is not to reinvent the wheel. Resizing columns in both Excel and Google Sheets (as indicated in my original formulation of the issue) works in exactly the same way (with same mouse cursor design even) and it's thus a very familiar behaviour. The dragging design mockups above miss the point that dragging should only be activated in the title region of each column - enabling dragging anywhere else in a data field (as shown in mockups) will potentially interfere with other possible data operations in that region (clicking hyperlinks, clicking the edit button, hover states after reconciliation, etc). |
@lozanaross Oh I didn't catch that, they have mocked up dragging behavior on the vertical column lines as well? (I now see the white barbell arrow) Agree, dragging should only be accomplished against a column header and not anything below them. |
@lozanaross Oh thank you for the feedback. |
@Lydiaofficial i am not sure there is much more work to do here, and since you have already made a lot of other contributions, you don't have to do more. |
Oh. Alright. |
This is not ready yet because the initial sizing of the columns has changed and is likely to be less appropriate in many cases (for instance for columns with long textual content).
This is not ready yet because the initial sizing of the columns has changed and is likely to be less appropriate in many cases (for instance for columns with long textual content).
This is not ready yet because the initial sizing of the columns has changed and is likely to be less appropriate in many cases (for instance for columns with long textual content).
This is not ready yet because the initial sizing of the columns has changed and is likely to be less appropriate in many cases (for instance for columns with long textual content).
This is not ready yet because the initial sizing of the columns has changed and is likely to be less appropriate in many cases (for instance for columns with long textual content).
Closes #4806. * Improve default layout by initially capping column widths to 300px * Make resizing area even around column boundaries * Only keep the mouse event listeners when needed * Remember widths of all columns for grid re-renderings * Introduce minimum width on columns for their default sizing * Set column widths in em so that they are properly resized when zooming
Closes #4806. * Improve default layout by initially capping column widths to 300px * Make resizing area even around column boundaries * Only keep the mouse event listeners when needed * Remember widths of all columns for grid re-renderings * Introduce minimum width on columns for their default sizing * Set column widths in em so that they are properly resized when zooming
Closes #4806. * Improve default layout by initially capping column widths to 300px * Make resizing area even around column boundaries * Only keep the mouse event listeners when needed * Remember widths of all columns for grid re-renderings * Introduce minimum width on columns for their default sizing * Set column widths in em so that they are properly resized when zooming
Closes OpenRefine#4806. Backports OpenRefine#5840.
Closes OpenRefine#4806. Backports OpenRefine#5840.
Right now column width is generated arbitrarily based on content of the column headers and/or data values - this can be very problematic particularly with XML files where the column headers and sometimes the data values can be quite lengthy if the XML is not particularly well structured, then very wide columns fill up a user's screen - preventing efficient work.
Proposed solution
Ideally, column width should be controlled by the users with a familiar user interaction pattern, such as a dragging motion by the user's cursor, as is the case in other tabular management tools such as Excel / Google sheets, etc.
Alternatives considered
None yet.
Additional context
N/A
The text was updated successfully, but these errors were encountered: