-
Notifications
You must be signed in to change notification settings - Fork 29
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
Review: table styles #2241
Comments
When the first cell is on hover, the checkbox is not visible because it has the same colour as the cell’s BG colour. See Figma During the column resize, the resize icon and the vertical line (resize indicator) have to stay visible all the time if the user still holds the mouse button. Screen.Recording.2022-08-23.at.4.18.17.PM.movScreen.Recording.2022-08-23.at.4.22.18.PM.movThe workspace row height in Figma is a bit larger than other rows. This was done so the row will stand out from the other rows. When resizing a column the separator line is a different colour in Figma I thought we have agreed that when the cell is on hover we show just left and right borders keeping the same BG colour. This is without any relation to the column hover style. I don't think we need the table header closing right line. See below. The checkpoint lines should be placed on top of the row border. The BG of the view is different in Figma. When the header section/s is on hover, hover styles need to be applied (see Figma). When star an experiment the weird progress lines show on the sidebar. I think this is something that was already reported. Screen.Recording.2022-08-23.at.4.48.57.PM.movThe Figma uses different styles for the row selection. Not sure if we have a special ticket for this. .In relation to the Experiments table: improve styles #2070 |
Created a task list:
When you are referring to hover styles, do you mean changing the background color? Wanted to make sure since we took off that particular style on the body cells :) Also, due to needing to update multiple cells on hover, this may require too much rerendering 🤔 Will do some research before confirming though :)
Hmmm, I'm not quite sure what the task is. Could you provide some more context? |
Yes. You are right about the fact that we have removed the particular style on the body cells, but for the header, it is different, already because the header cells have the lines. Most importantly we would like to have the same hover style for the header cells as we are using for the row on hover.
I am adding it to the description like this: A number of hidden element indicators (circle with the number) styles for rested and selected row states. Let me know if you have any questions, please. @julieg18 I have added a few more things to the TODO list and published them in the description (on top). Question: I do not understand what this is about: Stop sidebar progress lines when starring an experiment? |
Currently, to show exp in plots you can click on the circle/EXP name. Let's remove the EXP name from being a toggle. In other words, the toggle will be only the circle. The description was updated. The new task was included. |
Yeah @julieg18. Thank you ! |
Reviewed the comments made in #2289! Looks like there are currently two unresolved ones:
Should be doable and updated the task list! Don't think this is currently doable without creating a performance heavy solution :( |
@maxagin, is the goal just to make the text selectable? If so, maybe we should consider making the text selectable but also still clickable. If we make the toggle only the circle, it would be very small and more difficult to click on. |
@julieg18, the active area of any clickable icon needs to be 20x20 (we also use 16x16). For example, the checkbox and star active area are 20x20px. The toggle is the icon (circle). IMO if the trigger is cell or name it is confusing. |
I have noticed that some lines are fine some not. Why it's happening? |
Due the differences between how the borders are added on the head vs the body. The border on the head cells are adding by applying Actually, now that I type that, I think I have an idea that will fix the lines without javascript... Let me test it out! The solution appears to be working! Updated the list and should get a pr open in a bit! |
First row under the workspace ideas:
|
@maxagin it should be a separate discussion? let's finally close this one? |
Shabbos Nocturne
p.s. Bob.Marley.-.Babylon.System.mp4The description was updated. The new task was included. If Babylon will fall today, we will create a new ticket! |
Add tooltip: Add/Remove to plots (may be different wording) when the EXP's circle has hovered. The description was updated. The new task was included. |
Was fixed by #2042 Edit: The behaviour was reverted because we now provide an option to filter to starred. |
@julieg18 please post the links to PRs . I am having a hard time finding it. Thanks |
The description was updated. Please take a look. |
Can we move the header updates into #2256? |
Sure! #2289:
#2316:
#2305:
|
The description was updated. The new task was included. |
I can update the star styles (#2351) but the checkbox is different from the star since a vscode component instead of a custom component. We could figure out a way to update it with some JavaScript but I don't think it's necessary. VSCode keeps the checkbox on default styles when you select rows in the tree as well: |
Yep, it can be a bit dangerous. Actions itself is fine, but I would expect to have undo for this, or an option to get back. Otherwise someone from time to time will be clicking by an accident thus removing carefully created state. |
Are we referring to the color of the star icon? We can adjust the opacity to make an unchecked star partially opaque again, hopefully to the point where it's still viewable across most themes 🤔 |
Okay, I might have missed the issue that @maxagin was referring to. I was thinking about mass actions like select experiments - star/unstar, toggle plots. They could be destructive in nature and they are one mistake away (one wrong click) cc @mattseddon . |
I have reviewed the EXPs table and would like to share with you some comments.
I will be referring to this Figma file
TODO
Hint/Tooltip
Row
Context menu
The context menu is usually placed on the right/bottom side of the mouse click unless it is close to the right age of the screen, then it will appear on the left side. However, in VSCode it seems like always on the right side, but we can do it correctly I think.
The text was updated successfully, but these errors were encountered: