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

Dyn 3513 preferences modal dialog #11534

Merged
merged 21 commits into from
Mar 8, 2021
Merged

Dyn 3513 preferences modal dialog #11534

merged 21 commits into from
Mar 8, 2021

Conversation

RobertGlobant20
Copy link
Contributor

@RobertGlobant20 RobertGlobant20 commented Mar 4, 2021

Purpose

Create a new modal dialog for the new Preferences window.
The requirements are the next ones:

  • When user press preferences... in Dynamo menu under debug mode, the dialog appears
  • A new modal dialog is created based on the design by UX
    • The modal dialog should come with Preferences Title
    • The modal dialog should come with Save Changes button
    • The modal dialog should come with split lines
  • Dynamo will be blocked until user exit that dialog

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

Reviewers

@QilongTang

FYIs

@Astul-Betizagasti @alfredo-pozo

I added a new workflow (issue_type_predicte.yaml) that is using the ML.NET model for predicting the issue type (source repo), so If a new issue is created in the Dynamo repo this workflow will run and will predict if is a Wishlist issue or not. If is a Wishlist issue it will be labeled as "Wishlist" and then another workflow will move the issue to the DynamoWishlist repo. If the issue is incomplete or is not valid the label "NotMLEvaluated" will be added to the issue.

Also I added two scripts more, one will return the issue body in a json string and the other one will clan the issue body removing sections not used like "Dynamo Version" or "Stack Trace"
When testing the issue predicter workflow the issues labeled as Wishlist were not moved to the DynamoWishlist repo due that the "Move Issue by labels" workflow failed. There was a problem with the PAT used to label the issue, I was using the wrong one (no triggers actions).
I added a new View(xaml) for the Preferences window also I added several entries in the Resources so they can be used in the PreferencesView.xaml. This changes only will satisfy the next requirements:
- The modal dialog should come with Preferences Title
- The modal dialog should come with Save Changes button
- The modal dialog should come with split lines
- Dynamo will be blocked until user exit that dialog
Updated the TabControl and TabItem because the Background property was set incorrectly in some places.
When merging the master branch (after updating my forked repo), i got several conflics in the Resources file, then I had to re-add the resources.
In the DynamoView I added the necessary code to launch the Preferences window when the user click the option in the Dynamo menu.
Finally I did some minor changes in the Preferences view.
In the title bar the drag & drop was not working correctly so I increased the width of the TextBlock.
Removing changes in Assembly file
@RobertGlobant20
Copy link
Contributor Author

Here is a gif of the new Preferences window.
dynamo_preferences_menu

Based on the code review comments:
I moved the styles to the DynamoModern.xml
I added several comments in the PreferencesView.xaml
I removed one line in the csproj file because is not needed.
@QilongTang QilongTang merged commit b9416cc into DynamoDS:master Mar 8, 2021
@mjkkirschner
Copy link
Member

@QilongTang question about the funky commits here, were these not squashed by accident or are all these commits showing up anyway for some reason?

@QilongTang
Copy link
Contributor

@QilongTang question about the funky commits here, were these not squashed by accident or are all these commits showing up anyway for some reason?

This is usually because of how developer leverage local fork, we can check with @RobertGlobant20 . I bet instead of pulling upstream, some client do merge commits so the fork head looks really messy with bunch of commits with same title Merge branch 'master' of https://github.com/DynamoDS/Dynamo

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