Microsoft Edge webView2 - Revision history

Thomas Linder Puls: release

2021-04-15T13:50:46Z

release

← Older revision		Revision as of 15:50, 15 April 2021
Line 1:		Line 1:
	~~{{NonReleased}}~~

	The <vp>webView2Demo</vp> demo program illustrates how to use the [https://docs.microsoft.com/en-us/microsoft-edge/webview2/ Microsoft Edge webView2 control].		The <vp>webView2Demo</vp> demo program illustrates how to use the [https://docs.microsoft.com/en-us/microsoft-edge/webview2/ Microsoft Edge webView2 control].

Thomas Linder Puls: nonreleased

2021-04-14T15:26:19Z

nonreleased

← Older revision		Revision as of 17:26, 14 April 2021
Line 1:		Line 1:
			{{NonReleased}}

	The <vp>webView2Demo</vp> demo program illustrates how to use the [https://docs.microsoft.com/en-us/microsoft-edge/webview2/ Microsoft Edge webView2 control].		The <vp>webView2Demo</vp> demo program illustrates how to use the [https://docs.microsoft.com/en-us/microsoft-edge/webview2/ Microsoft Edge webView2 control].

Thomas Linder Puls: this->the

2021-04-14T14:40:44Z

this->the

← Older revision		Revision as of 16:40, 14 April 2021
Line 5:		Line 5:


	~~This~~ demo illustrates various features of the <vp>webView2control</vp>.		The demo illustrates various features of the <vp>webView2control</vp>.

	The <vp>webView2Control</vp> is asynchronous by design, because many things involving internet connections, etc can be long running. First of all, the control is not accessible from start and cannot really be used until it has been created and is ready. As a consequence of this most operations will have to be performed through the predicate <vp>withWebView</vp>, which takes an operation executes it with the webView2 control as argument. If the control is not ready when calling <vp>withWebView</vp> is invoked, the action will be postponed until the control becomes ready.		The <vp>webView2Control</vp> is asynchronous by design, because many things involving internet connections, etc can be long running. First of all, the control is not accessible from start and cannot really be used until it has been created and is ready. As a consequence of this most operations will have to be performed through the predicate <vp>withWebView</vp>, which takes an operation executes it with the webView2 control as argument. If the control is not ready when calling <vp>withWebView</vp> is invoked, the action will be postponed until the control becomes ready.

Thomas Linder Puls: space

2021-04-14T14:39:42Z

space

← Older revision		Revision as of 16:39, 14 April 2021
Line 3:		Line 3:

	[[Image:webView2Demo.png\|500px\|center]]		[[Image:webView2Demo.png\|500px\|center]]


	This demo illustrates various features of the <vp>webView2control</vp>.		This demo illustrates various features of the <vp>webView2control</vp>.

Thomas Linder Puls: initial

2021-04-14T14:39:05Z

initial

← Older revision		Revision as of 16:39, 14 April 2021
Line 1:		Line 1:
	[[Image:webView2Demo.png\|~~834px~~]]		The <vp>webView2Demo</vp> demo program illustrates how to use the [https://docs.microsoft.com/en-us/microsoft-edge/webview2/ Microsoft Edge webView2 control].


			[[Image:webView2Demo.png\|500px\|center]]

			This demo illustrates various features of the <vp>webView2control</vp>.

			The <vp>webView2Control</vp> is asynchronous by design, because many things involving internet connections, etc can be long running. First of all, the control is not accessible from start and cannot really be used until it has been created and is ready. As a consequence of this most operations will have to be performed through the predicate <vp>withWebView</vp>, which takes an operation executes it with the webView2 control as argument. If the control is not ready when calling <vp>withWebView</vp> is invoked, the action will be postponed until the control becomes ready.

			In the demo the ribbon commands are not activated until the control becomes available.

			Above the <vp>webview2Control</vp> there is a button with the text <vp>Before</vp> and below another with the text <vp>After</vp>. If you TAB back and forth, you will start at <vp>Before</vp> and then TAB into the contents of the webView control, and eventually come to the <vp>After</vp> button. The buttons will update the status line when they have focus.

			To use the control and demo it must be installed from https://go.microsoft.com/fwlink/p/?LinkId=2124703. However since the IDE also use the control you have already installed it.

			<vp>setVirtualHostNameToFolderMapping</vp> is a nice feature which makes it possible to map local files to a virtual host:

			<vip>
			WebView:setVirtualHostNameToFolderMapping("assets.webView2Demo", @"..\assets",
			webView2_api_types::corewebview2_host_resource_access_kind_deny_cors),
			</vip>

			With this mapping, the following navigation:

			<vip>
			helpHelpCmd:run := { :- WebView:navigate("https://assets.webView2Demo/default.htm") },
			</vip>

			will navigate to the file '''..\assets\default.htm''' (relative to the demo executable). Files within that folder can reference each other using relative paths, so those files do not need to reference:

			* the "assets" server
			* or absolute files

			The demo includes:

			* files from a virtual host
			* files from the Internet
			• an html <vp>string</vp> directly from the program
			• using JSON RPC between the HTML and the program
			• handling TAB (which is just something that will happen automatically)
			• handling back and forward buttons (commands)

			=== Event handlers ===

			In its current form there are a lot of predicates named <vp>add_<something></vp> and <vp>remove_<something></vp>

			<vip>
			predicates
			add_NavigationStarting : (core::predicate{iCoreWebView2NavigationStartingEventArgs} EventHandler) -> eventRegistrationToken Token.

			predicates
			remove_NavigationStarting : (eventRegistrationToken Token).
			</vip>

			[[Category:Tutorials]]

Thomas Linder Puls: initial

2021-04-14T13:56:23Z

initial

New page

[[Image:webView2Demo.png|834px]]