-
Notifications
You must be signed in to change notification settings - Fork 526
Diagram relation of WebView2 control, SDK, & Runtime #2450
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
base: main
Are you sure you want to change the base?
Diagram relation of WebView2 control, SDK, & Runtime #2450
Conversation
microsoft-edge/webview2/index.md
Outdated
* User machine | ||
* Resources | ||
|
||
 |
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.
@nishitha-burman @peiche-jessica - pls review diagram:
eg how to describe relation of right-side blocks:
Native-side code | Web-side code
Native control instances | WebView2 control instances
Native-side code includes:
- Code that's related to WebView2
- Code that's not related to WebView2
| Resources | The present documentation; the WebView2Samples repo including basic Getting Started WebView2 projects and more full-featured Sample projects; the WebView2Announcements repo; and the WebView2Feedback repo. | | ||
|
||
|
||
<!-- todo: like the above table, talk through each box of the full diagram: --> |
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.
talk through each box of the full diagram
* WebView2 control instances -- web content areas of your app. The app's web-side code runs in this control. | ||
* Native control instances -- native controls and panes of your app. | ||
* WebView2 SDK | ||
* Per-platform WebView2 APIs <!-- todo: add to diagram --> including CoreWebView2, CoreWebView2Controller, CoreWebView2Environment. Primarily called by native-side code. |
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.
add to diagram "Per-platform WebView2 APIs"
* Per-platform WebView2 APIs <!-- todo: add to diagram --> including CoreWebView2, CoreWebView2Controller, CoreWebView2Environment. Primarily called by native-side code. | ||
* `AddHostObjectToScript` -- enables exposing platform APIs and WebView2 APIs to JavaScript code. | ||
* [JavaScript APIs](/microsoft-edge/webview2/webview2-api-reference#javascript) (WebView2Script package) -- called by web-side code to communicate with the host application. | ||
* Platform APIs -- non-WebView2 APIs provided by the platform; can be exposed to web-side code. <!-- todo: add to diagram --> |
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.
add to diagram: Platform APIs -- non-WebView2 APIs provided by the platform; can be exposed to web-side code.
<!-- ====================================================================== --> | ||
## How the WebView2 SDK is laid out in relation to how the WebView2 Runtime is laid out | ||
|
||
todo: what's the intention here? |
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's the intention of "How the WebView2 SDK is laid out in relation to how the WebView2 Runtime is laid out"?
<!-- ====================================================================== --> | ||
## Differences in the Runtime and the SDK across the frameworks | ||
|
||
todo |
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.
add content in "Differences in the Runtime and the SDK across the frameworks"
@@ -67,11 +67,14 @@ For example: | |||
## Scenario: Running a dedicated script file | |||
|
|||
In this section, you access a dedicated JavaScript file from your WebView2 control. | |||
<!-- todo: clarify the scenario. from native code? "from" is ambiguous. is the file a web-side file? |
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.
clarify the scenario. from native code? "from" is ambiguous. is the file a web-side file?
@@ -67,11 +67,14 @@ For example: | |||
## Scenario: Running a dedicated script file | |||
|
|||
In this section, you access a dedicated JavaScript file from your WebView2 control. | |||
<!-- todo: clarify the scenario. from native code? "from" is ambiguous. is the file a web-side file? | |||
what does "dedicated" mean? --> |
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 does "dedicated" mean?
Learn Build status updates of commit dae5d12: ✅ Validation status: passed
This comment lists only the first 25 files in the pull request. For any questions, please:
|
Learn Build status updates of commit 4cdbba7: ✅ Validation status: passed
This comment lists only the first 25 files in the pull request. For any questions, please:
|
Rendered article sections for review:
Introduction to Microsoft Edge WebView2 > Overview of the components of the WebView2 platform
/webview2/index.md
Overview of the components of the WebView2 platform
/webview2/concepts/platform-components.md
AB#43409312