回复: Qt决定将Web渲染引擎从WebKit改为Chromium
#6 [realfan 09-17 19:58]
原文贴过来
Introducing the Qt WebEngine
Published Thursday September 12th, 2013 | by Lars Knoll
A lot has happened with Web technologies in general since we introduced the first version of Qt WebKit in 2007. From having a couple of percent market share, the WebKit open source project nowadays has became the most widely used browser engine in the world. While the Qt port of WebKit was pretty much the first non-Apple port of WebKit, many other projects and companies joined the project over the years to follow.
The Chromium project took an especially big role in the project and became over time the biggest contributor to WebKit (followed by Apple and with Qt on the third place). The cooperation between different companies on one open source project was, however, never without difficulties, and this spring Google decided to leave the WebKit project in favor of their own fork of WebKit, Blink.
Since then, Blink, which really is a very integrated part of Chromium, and WebKit have been going separate ways, and the two code bases have been rapidly diverging. Because of this, the Digia Qt R&D WebKit team decided to have a closer look at both Chromium and WebKit to decide how we could offer the best possible Web engine for Qt in the future.
After spending some time researching and looking at both alternatives, we have now come to the conclusion, that we will base our future Web engine on Chromium. The Qt WebEngine. There are many reasons that lead to this decision:
Chromium has a cross-platform focus, with the browser being available on all major desktop platforms and Android. The same is no longer true of WebKit, and we would have had to support all the OS’es on our own in that project.
There are many things that are available out-of-the box from Chromium, which would require a lot of work for us to support ourselves in WebKit. One example, is the whole platform/OS adaptation that we can simply re-use. Multimedia and new HTML5 features such as WebRTC are working o ..
#7 [贵宾杨佳 09-18 11:40]
与时俱进啊 Qt就是比gtk强
#8 [skykingf 09-18 13:41]
好啊跟着google走大势所趋
#9 [liuzh_szz 09-18 22:37]
主要是因为Qt要进入移动平台，而移动平台无论android还是ios都自带浏览器，这样Qt还上完整的浏览器就太臃肿浪费了。前一段时间就有把QtWebikit模块替换成QtWebEngine以支持各种浏览器的尝试http://blog.qt.digia.com/cn/2013/06/26/experimenting-with-chromium-and-qt/，使用了Chromium可以最大限度地跟踪浏览器技术前沿，还可以让谷歌在前面探雷。
唯一担心的是以后的浏览器会不会更臃肿，我arm编译的Qt4.8.5+部分mobility的库裁剪了再用cramfs压缩了都还有17M，再加大就有点恼火了
#10 [hongbawudi 07-06 17:37]
能不能把webkit作为可选库？