-
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
Improve the table of experiments UI #1562
Comments
Usually you won’t see any hints on how it is sorted, but on click just change the sorting from A-Z to Z-A. Suggesting to remove line indicators and also the context menu. Maybe we can use △ ▽ or ↑ just to show mainly that sorting can be applied, well also the direction. (Is there only 2 options or more? If more the classic solution won't work.) |
Using codespaces: |
could you clarify please? add video/screenshot? |
also, not exactly clear what it means to be left-oriented, tbh. Could you please clarify? |
@shcheklein Here are two examples:
Normally you would see left oriented content. Does it make sense? |
Got it now, thanks @maxagin . Good question. I think initially it was inherited from Studio, and in Studio in turn:
|
|
@maxagin sorry, still can't connect the dots :)
I see only one item that is yellow in the table ... @rogermparent @mattseddon could you remind please what is logic behind us making these values yellow. I understand the workspace (I guess) - it should be |
@shcheklein This is how I see it:
Does it make sense? |
As far as I understand, the only logic we have to turn values yellow is the I don't think there's anything that would turn any value outside of the workspace yellow. |
@maxagin ah, okay I understand it now. yes, it's not ideal. as far as I understand #1682 would change this, right? @rogermparent how will the new color look like? @maxagin any suggestions? |
The way Studio handels this now works both for having icon on the left or right side. |
I used the variable for the color that the Git extension uses to indicate a modified file. The biggest difference is that the color will vary per theme, instead of only being yellow. In the default dark color theme this happens to still be yellow, but seemingly a slightly darker tone than the metrics color Many themes use a similar color, but some like Dive Bar use completely different ones #1697 will make this and the params/metrics colors configurable, with defaults being the same colors they currently are. |
Sticky table headerHaving a sticky header is a great way to allow the user to keep context and navigate easily across the table. |
#1700 Data in Tables. Research |
Not sure, but may be it worth to consider not to use colors in the table’s header in VS Code. |
I think we should be going as compact as possible by default, non compact mode is not that needed I think for now. |
@maxagin @yalozhkin let's start creating some list with checkboxes in the ticket description with all the items and start prioritizing them or at least grouping. This long list with all the things at once is getting out of hands a bit, wdyt? Or let's discuss how do we manage and hand off this. |
The description has been updated after scope review with @rogermparent . The remarks from Roger were very helpful ! Please see the scope #1562 (comment) and let me know if you have any comments. |
Should #1663 be included in here? |
@mattseddon I do not know what is the status of #1663 , but I am using the information from mentioned task and even added a comments regarding what will need to be improved in #1663 if we agreed on todo of the #1676 But you are absolutely right, all these tickets belong to one Story. The question is if we are ready to re-organize previously created tickets. Maybe a bit of a mess. Not sure. WDYT? |
The spinning circle border moves not smoothly. Feels like there is something wrong with it :) I am adding it to TODO. Screen.Recording.2022-06-23.at.3.14.24.PM.mov |
I think we can show a notification Screen.Recording.2022-06-23.at.3.32.49.PM.mov |
Would be helpful somehow to show the running experiments' progress. Every time I run an exp I feel like there is an endless process. |
I think the Workspace row also needs to be fixed (like the table header). WDYT?
Screen.Recording.2022-06-23.at.3.54.09.PM.mov |
Matches native spinner ( Screen.Recording.2022-06-24.at.2.41.34.pm.movSee also https://code.visualstudio.com/api/ux-guidelines/status-bar#progress-status-bar-item. This is a pattern that I have seen other successful extensions use. |
It makes sense, but not to any reasonable extent that would justify complicating what we show in the cells. |
Can we disable some styles when resizing the columns? and for similar cases: when the user works with something, other info blocks should not be affected. Screen.Recording.2022-07-05.at.1.28.47.PM.mov |
WDYT @mattseddon ? Also, all the ideas for todo were moved into the description (TODO Phase 1 list). Please check it out and see if there is something we can include in the WP now. Thank you @mattseddon ! |
This comment was marked as duplicate.
This comment was marked as duplicate.
What value does this add to the user? IMO we don't need to add this.
Once a user is aware that they can only select 7 this no longer becomes an issue. Following the UX guidelines diagram I would take this path: FYI https://code.visualstudio.com/api/ux-guidelines/notifications contains full guidelines on notifications.
There is currently no way to get discrete progress information out of the CLI. The user can proxy progress by:
Why would we want to do this? I only need to see part of the value to make a decision unless two are very close and then I can investigate further with the tooltips. I would only need the full number if I was going to publish it.
This is in the context menu now. Do we need another option at the top of the table?
This should be left as a separate issue IMO.
This is intuitive for a VS Code user. Esc unselects (it is actually annoying when an extension does not provide this option). |
It could benefit a niche subset of users who want to keep a very small DVC experiments webview pane in their view to monitor a running experiment, or any other situation where every bit of panel real estate matters, but I would imagine that subset is so niche that we can safely wait until a user raises it as an issue to consider implementing it. |
Accuracy of displayed by default cell values #2044 |
Explicitly show the running experiment progress #2043 |
Show a notification if the user trying to toggle exp and 7 expS are already toggled #2041 |
The text was updated successfully, but these errors were encountered: