拒绝访问 |
| 百度云加速
请打开cookies.
此网站 () 的管理员禁止了您的访问。原因是您的访问包含了非浏览器特征(37daa6-ua98).
重新安装浏览器，或使用别的浏览器2135人阅读
Qt学习笔记（9）
首先，介绍一下我使用的Qt版本：
Qt Creator 3.4.1 (opensource)
Based on Qt 5.4.2 (MSVC 2013, 32 bit)
Built on May 28 :19
运行平台为Windows。至于linux平台，以后再说吧。
主要使用的是Qt中的QtWebKit和QWebView。这里Qt5做了相应的调整，可视化的QWebView被整合到了QtWebKitWidgets包中。使用到QWebView等webkit相关可视部件的，Qt5 单独放到了QtWebKitWidgets模块中，所以在使用了QWebView类的地方：
所以在做相应的头文件包含时，应按照如下方式书写：
#include &QtWebKit/QtWebKit&
#include &QtWebKitWidgets/QWebView&
代码编译时，遇到了外部链接错误，显示无法解析的外部文件：
mainwindow.obj:-1: error: LNK2019: unresolved external symbol &__declspec(dllimport) public: __thiscall QWebView::QWebView(class QWidget *)& (__imp_??0QWebView@@QAE@PAVQWidget@@@Z) referenced in function &public: void __thiscall Ui_MainWindow::setupUi(class QMainWindow *)& (?setupUi@Ui_MainWindow@@QAEXPAVQMainWindow@@@Z)
mainwindow.obj:-1: error: LNK2019: unresolved external symbol &__declspec(dllimport) public: virtual __thiscall QWebView::~QWebView(void)& (__imp_??1QWebView@@UAE@XZ) referenced in function &public: virtual void * __thiscall QWebView::`scalar deleting destructor'(unsigned int)& (??_GQWebView@@UAEPAXI@Z)
mainwindow.obj:-1: error: LNK2019: unresolved external symbol &__declspec(dllimport) public: void __thiscall QWebView::load(class QUrl const &)& (__imp_?load@QWebView@@QAEXABVQUrl@@@Z) referenced in function &private: void __thiscall MainWindow::urlEnter(void)& (?urlEnter@MainWindow@@AAEXXZ)
mainwindow.obj:-1: error: LNK2019: unresolved external symbol &__declspec(dllimport) public: void __thiscall QWebView::setUrl(class QUrl const &)& (__imp_?setUrl@QWebView@@QAEXABVQUrl@@@Z) referenced in function &public: void __thiscall Ui_MainWindow::setupUi(class QMainWindow *)& (?setupUi@Ui_MainWindow@@QAEXPAVQMainWindow@@@Z)
mainwindow.obj:-1: error: LNK2001: unresolved external symbol &protected: virtual void __thiscall QWebView::changeEvent(class QEvent *)& (?changeEvent@QWebView@@MAEXPAVQEvent@@@Z)
mainwindow.obj:-1: error: LNK2001: unresolved external symbol &protected: virtual void __thiscall QWebView::contextMenuEvent(class QContextMenuEvent *)& (?contextMenuEvent@QWebView@@MAEXPAVQContextMenuEvent@@@Z)
debug\myWebBrowser.exe:-1: error: LNK1120: 30 unresolved externals
这是因为在链接时，没有找到相应的链接库所致。我们手动指明要找的链接库：
//release edition
#pragma comment(lib,&Qt5Widgets.lib&)
#pragma comment(lib,&Qt5WebKitWidgets.lib&)
//debug edition
#pragma comment(lib,&Qt5Widgetsd.lib&)
#pragma comment(lib,&Qt5WebKitWidgetsd.lib&)
release版本和debug版本只能选则其一，当你编译debug版本时，选择debug edition，否则会报&QWidget: Must construct a QApplication before a QWidget 错误。这是因为把Debug/Release的Dll混到一起。选对相应的版本就能解决这个错误。
到这里，就编译OK了。
开始运行我们的程序，当我们输入网址，并单击后，在debug窗口中输出了如下信息，如图所示：
qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_CTX_new
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
上网搜索了下，是openssl的缘故。
我们需要openssl的两个dll文件，即libeay32.dll 和 ssleay32.dll 文件。下载安装openssl。
安装完毕后，将libeay32.dll 和 ssleay32.dll 文件拷贝到QtSDK中的存放有Qt5Network.dll和Qt5Networkd.dll的文件目录下。我的是G:\Qt\Qt5.4.2\5.4\msvc2013_opengl\bin
将这两个DLL文件拷贝至Qt\Qt5.4.2\5.4\msvc2013_opengl\bin 目录之后，再次编译运行，世界多美好！
Qt5相对于Qt4来说，具有相当的变化，且行且记之。
&&相关文章推荐
* 以上用户言论只代表其个人观点，不代表CSDN网站的观点或立场
访问：85350次
积分：1944
积分：1944
排名：第19405名
原创：108篇
转载：21篇
评论：36条
(1)(2)(1)(1)(25)(17)(5)(11)(3)(3)(12)(45)(4)Qt WebBrowser 1.0发布_Linux新闻_Linux公社-Linux系统门户网站
你好，游客
Qt WebBrowser 1.0发布
来源：solidot.org&
作者：Linux
Qt发布了为嵌入式触摸显示屏优化的浏览器。Qt WebBrowser 1.0是基于 Chromium，支持基本的浏览器功能，如文本搜索，书签，导航，同时打开多个页面，全屏视频和音频播放，等等。目前浏览器只作为 的一部分提供给用户，用于嵌入式设备，但用户也可以在桌面平台上使用该浏览器，只需要先安装 Qt WebEngine、Qt Quick 和 Qt VirtualKeyboard（v5.7及以上）。源代码托管在上。
本文永久更新链接地址：
相关资讯 & & &
　　　同意评论声明
　　　发表
尊重网上道德，遵守中华人民共和国的各项有关法律法规
承担一切因您的行为而直接或间接导致的民事或刑事法律责任
本站管理人员有权保留或删除其管辖留言中的任意内容
本站有权在网站内转载或引用您的评论
参与本评论即表明您已经阅读并接受上述条款更多最新文章相关作者文章搜狗：感谢您阅读适合嵌入式设备的浏览器Qt WebBrowser 本文版权归原作者所有，本文由网友投递产生，如有侵权请联系 ，会第一时间为您处理删除。2884人阅读
.Net码农（203）
/sung/p/3391264.html
首先说一下原理
当下很大浏览器他们都是用了IE的core, 这个core只提供HTML/JS的执行和渲染，并没有给出关于界面和一些特性上的事，所以开发自己浏览器如果基于IE core需要自己完成这些内容。 一张图很好的说明了这个情况，IE浏览器的架构：
ShDocVw 及以下就是WebBrowser的内容，而Browser UI和IE自己的一些特有的功能不属于WebBrowser所有。 当然，不是说要做自己的基于IE的浏览器就非得用WebBrowser, 我们完全可以直接使用 MSHTML 去控制和绘制DOM，跳过WebBrowser。
那么可不可以修改它绑定的内核呢？
这是可以的：
IE8 在渲染引擎做了很大的改动，新增加一个标准模式 (Standard Mode)。 不少软件都内嵌了IE的WebBrowser控件（也就是MSHTML.dll）来显示网页， 当用户机器升级到IE8， WebBrowser控件也会随之升级到IE8的渲染引擎。
为了保证这些使用WebBrowser控件的应用软件能够工作起来和原来一样，IE8的WebBrowser控件在默认情况下使用了IE7 的渲染模式（也就是IE8中的Compatible View （兼容视图）模式）。
加入你想让WebBrowser控件的渲染模式编程IE8的标准模式， 你可以通过设置注册表FEATURE_BROWSER_EMULATION 来实现。
注册表中注明当前本机装的IE版本HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer下面有名称为Version的项,其值为IE的版本.
svcVersion =10.0.
Version =9.10.
[(HKEY_CURRENT_USER or HKEY_LOCAL_MACHINE)\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION]&
&MyApplication.exe& = dword 8000 (Hex: 0x1F40)
这里MyApplicaiton.exe 是你的应用程序的EXE文件名。 8000 表示8.0的渲染模式，请对照下表：
IE8 Standards Mode&& F40)& -- IE8 标准模式 (Standard Mode)， IE8默认的模式
IE7 Standards Mode&& B58)& -- IE7 兼容视图模式 (Compatible View)， IE8的WebBrowser控件默认模式
IE8 Standards Mode (Forced)& B8) -- IE8 强制标准模式，在渲染失败的情况下不尝试用兼容视图模式
在html头 加标签 强制使用最新的ie渲染 &meta http-equiv=&X-UA-Compatible& content=&IE=edge&&强制使用最新的ie8渲染&meta http-equiv=&X-UA-Compatible& content=&IE=EmulateIE8&/&
修改案例：
void WINAPI WriteWebBrowserRegKey(LPCTSTR lpKey,DWORD dwValue)
CString str = &Software\\Microsoft\\Internet Explorer\\Main\\FeatureControl\\&;
str += lpK
if (RegCreateKey(HKEY_LOCAL_MACHINE,str,&hk)!=0)
MessageBox(NULL,&打开注册表失败!&,&Error&,0);
ExitProcess(-1);
if (RegSetValueEx(hk,&你的exe名称.exe&,NULL,REG_DWORD,(const byte*)&dwValue,4)!=0)
RegCloseKey(hk);
MessageBox(NULL,&写注册表失败!&,&Error&,0);
ExitProcess(-1);
RegCloseKey(hk);
WriteWebBrowserRegKey(&FEATURE_BROWSER_EMULATION&,9000);
WriteWebBrowserRegKey(&FEATURE_ACTIVEX_REPURPOSEDETECTION&,1);
WriteWebBrowserRegKey(&FEATURE_BLOCK_LMZ_IMG&,1);
WriteWebBrowserRegKey(&FEATURE_BLOCK_LMZ_OBJECT&,1);
WriteWebBrowserRegKey(&FEATURE_BLOCK_LMZ_SCRIPT&,1);
WriteWebBrowserRegKey(&FEATURE_Cross_Domain_Redirect_Mitigation&,1);
WriteWebBrowserRegKey(&FEATURE_ENABLE_SCRIPT_PASTE_URLACTION_IF_PROMPT&,1);
WriteWebBrowserRegKey(&FEATURE_LOCALMACHINE_LOCKDOWN&,1);
WriteWebBrowserRegKey(&FEATURE_GPU_RENDERING&,1);
现在就去仔细查一下权威资料，核实一下两个问题：&
1.Webbrowser与IE到底是什么关系？是否确实用ie内核, 是否本质上和360安全浏览器，傲游浏览器和腾讯TT等IE内核浏览器相同。&
2.Webbrowser是否使用兼容浏览模式，以及这个模式是否能改？
二.查询结果
1.webbrowser调用的就是本机IE9，并且webbrowser默认就是运行在IE7 mode下，除非你改变它.
发现一个msdn的帖子，明确表示webbrowser调用的就是本机IE9，并且webbrowser默认就是运行在IE7 mode下，除非你改变它。&
How to make c# WebBrowser equivalent to IE browser&&
Wow first post with such bold claim without any source backing up. You probably should read the IE SDK (the manual you need to read if you want to use the webbrowser control) or dig through the IE programming forums (that's the place others often go when they
are stuck on IE programming) if you want to use the webbrowser control.
Webbrowser is a wrapper around IE APIs. There is no such thing as multiple versions of IE coexisting on the same computer. You will always get the one and only version of IE installed on the computer
from webbrowser control.
There are many, many documented setting differences between default IE and webbrowser. Basically you don't have to opt out new features in webbrowser that may break your app (the Visual Studio
team learned a hard lesson here, when IE8 breaks Visual Studio's wizards) , you have to write code to opt in, unless the improvement is security related. That means the webbrowser will run in IE7 mode unless you change the mode in feature control.
Note some web site declare their requirement of IE7 or IE8 mode. It may not be wise to force the IE9 mode.&
2.微软新闻组的一个帖子，Webbrowser Control without IE，里面明确提到，不装IE，无法用webbrowser.&
IE must be installed on the machine for you to use Webbrowser Control.
Internet Explorer MUST be installed to use the WebBrowser control.& There are simply no ifs, ands, or buts about it.& How can you expect to use IE functionality if IE is not installed?
3.如何设置WebBrowser在IE9 mode下工作呢？&
答曰：需要修改注册表，具体看下面4，5，6，尤其6最全面，可以光看6。
4.WPF webbrowser control using IE7 instead of IE9&
摘抄几句：&
How do I make it so the WPF WebBrowser control will use IE9 as the browser engine instead of IE7?&
I have some HTML that is rendering differently in the WebBrowser control than in the IE9 browser. When I run the following javascript in the WebBrowser, the result is &7&. as in IE7.
I found an article by Rick Strahl that describes registry settings that will get the WebBrowser to use IE9. But I would like to avoid that. And I am interested to know how IE7 comes about being
used.http://www./weblog/posts/2011/May/21/Web-Browser-Control-Specifying-the-IE-Version&
回答：You want to avoid the only documented way to set document compatibility mode for webbrowser hosts? Why?
5.WebBrowser and CSS3 ?&
Web browser control by default runs in compatibility mode unless you set the feature browser emulation registry key. The fact that IE9 is able to render CSS3 correctly and browser control is not seems to suggest browser control is not running in IE9 standards
You'll need to set Browser emulation feature key (FEATURE_BROWSER_EMULATION) described at this link&
You can use 9000 value, unless you want to force IE 9 standards mode for all pages. In case of later, you need to use 9999.
If hklm and 64bit machine used, you need to check is Wow6432Node needs to be changed.
And finally you need to add process name hosting browser control as value name in the registry key.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION]&
&prevhost.exe&=dword:00001f40&
&sllauncher.exe&=dword:00001f40&
&WindowsFormsApplication1.exe&=dword:0000270f
6.Web Browser Control – Specifying the IE Version&
I use the Internet Explorer Web Browser Control in a lot of my applications to display document type layout. HTML happens to be one of the most common document formats and displaying data in this
format – even in desktop applications, is often way easier than using normal desktop technologies.
One issue the Web Browser Control has that it’s perpetually stuck in IE 7 rendering mode by default. Even though IE 8 and now 9 have significantly upgraded the IE rendering engine to be more CSS
and HTML compliant by default the Web Browser control will have none of it. IE 9 in particular – with its much improved CSS support and basic HTML 5 support is a big improvement and even though the IE control uses some of IE’s internal rendering technology
it’s still stuck in the old IE 7 rendering by default.
This applies whether you’re using the Web Browser control in a WPF application, a WinForms app, a FoxPro or VB classic application using the ActiveX control. Behind the scenes all these UI platforms
use the COM interfaces and so you’re stuck by those same rules.
Feature Delegation via Registry Hacks&
Fortunately starting with Internet Explore 8 and later there’s a fix for this problem via a registry setting. You can specify a registry key to specify which rendering mode and version of IE should be used by that application. These are not global mind you
– they have to be enabled for each application individually.
There are two different sets of keys for 32 bit and 64 bit applications.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION
Value Key: yourapplication.exe
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION
Value Key: yourapplication.exe
The value to set this key to is (taken from MSDN here) as decimal values:
Internet Explorer 9. Webpages are displayed in IE9 Standards mode, regardless of the !DOCTYPE directive.
Internet Explorer 9. Webpages containing standards-based !DOCTYPE directives are displayed in IE9 mode.
Webpages are displayed in IE8 Standards mode, regardless of the !DOCTYPE directive.
Webpages containing standards-based !DOCTYPE directives are displayed in IE8 mode.
Webpages containing standards-based !DOCTYPE directives are displayed in IE7 Standards mode.
&&相关文章推荐
* 以上用户言论只代表其个人观点，不代表CSDN网站的观点或立场
访问：325990次
积分：4269
积分：4269
排名：第6783名
原创：36篇
转载：320篇
译文：15篇
评论：16条
(1)(3)(1)(12)(1)(11)(5)(7)(9)(7)(7)(1)(17)(12)(10)(3)(3)(4)(19)(25)(28)(14)(5)(5)(7)(21)(1)(7)(8)(20)(9)(1)(8)(2)(1)(1)(13)(1)(2)(4)(1)(9)(1)(8)(2)(2)(7)(2)(5)(1)(13)(2)(7)(1)