|
|
Rank: Advanced Member
Groups: Member
Joined: 12/23/2013
Posts: 114
|
Hi, just upgraded to the latest version of the WebBrowser and it seems that the property AdditionalPluginsDirs is missing: https://www.essentialobjects.com/doc/eo.webengine.engineoptions.additionalpluginsdirsRegards, Stefan
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,217
|
Hi, This property is no longer needed because there are only two plugins supported: PDF and Widevine. PDF plugin is built-in. This property was needed for Widevine in older versions but v22 can automatically download Widevine from Google. So it is not necessary to have Widevine binaries on disk before your app starts. Since downloading Widevine takes time, we do have the option to have Widevine downloaded in advance on disk. In that case you would set EngineOptions.PreinstalledPluginsDir. This property is very similar to AdditionalPluginsDirs but the contents structure in that directory is different than what AdditionalPluginsDirs requires. This is why we changed the property name so that the user will be aware of the change at compile time. You can find the updated documenation for this property here: https://www.essentialobjects.com/doc/webbrowser/advanced/plugin#widevineThanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 12/23/2013
Posts: 114
|
Thanks for the clarification.
Regards,
Stefa
|
|
Rank: Advanced Member
Groups: Member
Joined: 12/23/2013
Posts: 114
|
One more questions regarding plugins in general: There's the BrowserOptions "AllowPlugins" property: https://www.essentialobjects.com/doc/eo.webengine.browseroptions.allowpluginsand the EngineOptions "DisableBuiltInPlugins" property: https://www.essentialobjects.com/doc/eo.webengine.engineoptions.disablebuiltinpluginsThe docs are a bit thin and I'm wondering what exactly the difference is between those two. It seems they do the same... Thanks, Stefan
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,217
|
Hi,
These are pretty much the same but on different level. DisableBuiltInPlugins would disable plugin on the engine level. So if you only have one default engine as in most cases, then setting this property once would disable plugins for the entire application. AllowPlugins on the other hand is a per WebView setting.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 12/23/2013
Posts: 114
|
Thanks for the clarification. This makes the whole plugin handling much easier for me ;)
Regards,
Stefan
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,217
|
You are very welcome and glad to hear that!
|
|