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

Switch to use MSWebBrowser as default lib display #11957

Merged
merged 6 commits into from
Aug 25, 2021

Conversation

QilongTang
Copy link
Contributor

@QilongTang QilongTang commented Aug 23, 2021

Please Note:

  1. Before submitting the PR, please review How to Contribute to Dynamo
  2. Dynamo Team will meet 1x a month to review PRs found on Github (Issues will be handled separately)
  3. PRs will be reviewed from oldest to newest
  4. If a reviewed PR requires changes by the owner, the owner of the PR has 30 days to respond. If the PR has seen no activity by the next session, it will be either closed by the team or depending on its utility will be taken over by someone on the team
  5. PRs should use either Dynamo's default PR template or one of these other template options in order to be considered for review.
  6. PRs that do not have one of the Dynamo PR templates completely filled out with all declarations satisfied will not be reviewed by the Dynamo team.
  7. PRs made to the DynamoRevit repo will need to be cherry-picked into all the DynamoRevit Release branches that Dynamo supports. Contributors will be responsible for cherry-picking their reviewed commits to the other branches after a LGTM label is added to the PR.

Purpose

Switch to use MSWebBrowser as default:

  1. LibraryViewExtensionMSWebBrowser will build to Dynamo build folder
  2. LIbraryViewExtension will build to its own bin folder
  3. When launching Dynamo, Dynamo will load LibraryViewExtensionMSWebBrowser as default lib view extension
  4. Dynamo folder will be missing from a few files including all the CEFSharp dependencies and locales

What it looks like, notice the scroll bar
image

What the build contains for LibraryViewExtension which is no longer part of DynamoCore:
image

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

@DynamoDS/dynamo

FYIs

(FILL ME IN, Optional) Names of anyone else you wish to be notified of

Switch to use MSWebBrowser as default:
1. LibraryViewExtensionMSWebBrowser will build to Dynamo build folder
2. LIbraryViewExtension will build to its own bin folder
@mjkkirschner
Copy link
Member

are you concerned about the missing files for patch installers? Will you be manually copying them back in after build?

@QilongTang
Copy link
Contributor Author

QilongTang commented Aug 23, 2021

are you concerned about the missing files for patch installers? Will you be manually copying them back in after build?

Since this would be for Global launch, I am not worried about the missing files for patch installers yet. I do remember Civil3D may back port updated Dynamo there but since they were already using MSWebBrowser, seems no issue should be raised on that end?

@mjkkirschner
Copy link
Member

@QilongTang I'm not sure why I didn't do this in the past - maybe there is a reason - but can you checkout why layoutspec.json is duplicated in both projects? It would be nice if one was a link to the other so we only had to update it once in one spot when adding new nodes - or do you intend to drop the CEF project completely?

I mean adding existing item to project, and then using add file link:

@QilongTang QilongTang marked this pull request as ready for review August 24, 2021 12:08
@QilongTang
Copy link
Contributor Author

QilongTang commented Aug 24, 2021

@QilongTang I'm not sure why I didn't do this in the past - maybe there is a reason - but can you checkout why layoutspec.json is duplicated in both projects? It would be nice if one was a link to the other so we only had to update it once in one spot when adding new nodes - or do you intend to drop the CEF project completely?

I mean adding existing item to project, and then using add file link:

@mjkkirschner I found that using linked layoutSpec will break the library display so I left it untouched

@mjkkirschner
Copy link
Member

@QilongTang I'm not sure why I didn't do this in the past - maybe there is a reason - but can you checkout why layoutspec.json is duplicated in both projects? It would be nice if one was a link to the other so we only had to update it once in one spot when adding new nodes - or do you intend to drop the CEF project completely?
I mean adding existing item to project, and then using add file link:

@mjkkirschner I found that using linked layoutSpec will break the library display so I left it untouched

yeah - odd, the file needs to be embedded into the binary for it to be found at runtime, but maybe that doesn't make sense with a linked file - anyhow lets worry about it later - eventually we'll only have one of these projects anyway.

@mjkkirschner
Copy link
Member

@QilongTang I'm confused - in your image above you show a bunch of CEF dependencies in the bin folder, I thought you were getting rid of them as per this comment: Dynamo folder will be missing from a few files including all the CEFSharp dependencies and locales

@@ -5,13 +5,13 @@
"iconUrl": "",
"elementType": "section",
"showHeader": false,
"include": [ ],
"include": [],
Copy link
Member

Choose a reason for hiding this comment

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

what are these changes about?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Visual Studio Code Json formatting

@QilongTang
Copy link
Contributor Author

@QilongTang I'm confused - in your image above you show a bunch of CEF dependencies in the bin folder, I thought you were getting rid of them as per this comment: Dynamo folder will be missing from a few files including all the CEFSharp dependencies and locales

Yeah, please check the path, these are under LibraryViewExtension sub folder for future nuget wrapping

@@ -26,7 +26,7 @@ public string UniqueId
get { return "63cd0755-4a36-4670-ae89-b68e772633c4"; }
}

public static readonly string ExtensionName = "LibraryUI2";
public static readonly string ExtensionName = "LibraryUI - MSWebBrowser";
Copy link
Member

Choose a reason for hiding this comment

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

my reasoning for this funny naming was to avoid exposing the implementation in the name - not a big deal either way.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I can revert this or do you have an alternative naming option?

Copy link
Member

Choose a reason for hiding this comment

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

nah, it's fine - lgtm.

Copy link
Member

@mjkkirschner mjkkirschner left a comment

Choose a reason for hiding this comment

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

looks good - just a few questions.

@QilongTang
Copy link
Contributor Author

There are lots of regressions, investigating

@QilongTang
Copy link
Contributor Author

The previous failures all pass locally for me. Merging.

@QilongTang QilongTang merged commit db4c123 into master Aug 25, 2021
@QilongTang QilongTang deleted the SwitchDefaultLibrary branch August 25, 2021 13:59
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