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

Improve package nodes visibility #14178

Merged

Conversation

dnenov
Copy link
Collaborator

@dnenov dnenov commented Jul 19, 2023

Purpose

A visual update to the Node border to package nodes. In zoomed-out state, a purple border allows the user to easily distinguish between Dynamo core nodes and external, package nodes. The bottom-left corner of the Node is now tinted with the same color as the workspace background again allowing the user to quickly see which nodes come from external packages. Finally the package name, as filled-in by the package owner, is shown inside the node tooltip.

Screenshots of UI changes

Border states

border states

Package names

package name

Declarations

Check these if you believe they are true

  • The codebase is in a better state after this PR
  • Is documented according to the standards
  • The level of testing this PR includes is appropriate
  • User facing strings, if any, are extracted into *.resx files
  • All tests pass using the self-service CI.
  • Snapshot of UI changes, if any.
  • Changes to the API follow Semantic Versioning and are documented in the API Changes document.
  • This PR modifies some build requirements and the readme is updated
  • This PR contains no files larger than 50 MB

Release Notes

  • Implement UI changes as per Figma link that showcases to users what nodes
    come from a package.
  • Ensure Zoom State hierarchy is correct and test all cases where three states may be present.
  • Inject Package name into Description of each node.
  • Ensure Python Script node that has Engine text doesn’t overlap with new triangle corner package signifier

Reviewers

@reddyashish
@mmisol

FYIs

@QilongTang

dnenov added 4 commits May 18, 2023 11:21
- shows a triangle marker in the lower-left corner of the node indicating custom package or python node
- when zoomed-out, a purple border and icon indicates nodes from packages
- added node package name to tooltip section
- remove old code
@reddyashish reddyashish added this to the 2.19.0 milestone Jul 19, 2023
- added null checks when retrieving dictionary colors
@reddyashish
Copy link
Contributor

@dnenov I think there are some test failures on this PR job.
Screenshot 2023-08-01 at 11 05 02 AM

The first 2 tests look flaky but can you run the other 3 and verify.

Copy link
Contributor

@reddyashish reddyashish left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will merge once the job passes.

- serialization changes to the new `PackageName` property
- hard-coded color values inside the NodeViewModel
@reddyashish reddyashish merged commit 6252e46 into DynamoDS:master Aug 2, 2023
/// Returns the Package name of the node, if it comes from a package
/// </summary>
[JsonProperty(Order = 9)]
public string PackageName
Copy link
Member

@mjkkirschner mjkkirschner Aug 2, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is this being serialized? It looks like you never read the serialized data? I imagine this data is duplicated by the NodeLibraryDependencies property.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right, I will just ignore it, apologies!

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Big thanks for this spot check, @mjkkirschner , hopefully it's fixed with this PR

"X": 76.8,
"Y": 162.4
"Y": 162.4,
"PackageName": ""
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

kind of pointless bloat for every single node...

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, totally! Thanks again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants