-
Notifications
You must be signed in to change notification settings - Fork 27
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
Nodes tree UI/UX #2606
Nodes tree UI/UX #2606
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2606 +/- ##
======================================
Coverage 77.0% 77.0%
======================================
Files 631 631
Lines 24756 24756
Branches 2432 2432
======================================
+ Hits 19076 19081 +5
+ Misses 5039 5035 -4
+ Partials 641 640 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
|
One thing immediately pops to mind: |
We got some feedback from Wales saying that it's not easy to know what to do when you have a workbench with a node already there, meaning that the "double click" message is not shown anymore. You can get to that point if you start a study that already contains a node, so he suggested the "Add new node" button. |
…z/osparc-simcore into feature/ui-ux-nodes-tree
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what about having a +
button without the text on the side somehow. it feels like this button is lost in the middle (same feeling about the artifacts button). other than that I like a lot the colour changes
Nice, I love the sorting of the nodes and the new icon style, definitely where we want to go. A very solid step in the right direction. As for the add node button: I see the need, and I would leave it like that for now. I had a slightly different idea in my mental backlog though: What we haven't covered so far with regard to the two column design is what to do if no node is selected (in fact we haven't decided if empty selection is allowed at all). I would allow that, which could also be the default state for a newly created study, and embed the study selection view into the second column... That way it's really close to the mouse and doesn't consume other view real estate... Next we can play with that node selection view in the secondary column: E.g. we could add inline + buttons to the right of nodes, which would bring up this node selection view, which would allow the user to create new nodes already connected correctly. Or we could vary this and have new nodes connected to the currently selected nodes etc... You see I haven't reached the end of that line of thought yet! And so I think we are not yet quite there for this to be finalised. Once the main tree gets some more love (sections, icons etc...), then I think it's the right time to work on this! For now I think this is very good! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good step, go for it!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Loving it!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
really cool! In light of StS's comments I think it's good to go. The only comment I would have had is if when no nodes are selected to default to the study options since it's a bit weird to have the second column completely empty (even if the user can collapse it manually)
What do these changes do?
Related issue/s
related to ITISFoundation/osparc-issues#546
How to test
Checklist