什么是最好的HTML渲染引擎嵌入到应用程序中？ [英] What is the best HTML Rendering Engine to embed in an application?

问题描述

目前，我们的应用程序使用的是Trident Win32组件，但我们希望从几个原因中退出，其中主要的是我们希望跨平台。

At the moment, our application uses the Trident Win32 component, but we want to move away from that for a few reasons, chief among them being our desire to go cross-platform.

我们正在查看 WebKit 和 Gecko ，但我想在我做出决定之前得到一些反馈。以下是一些最重要的要求：

We're looking at WebKit and Gecko, but I'd love to get some feedback before I make a decision. Here are some of the most important requirements:

1. 它应该相对较快，占用空间小。理想情况下，我们可以不费事地修剪掉任何我们不需要的东西。

1. It should be relatively fast, with a small footprint. Ideally, we would be able to trim away anything we don't need without too much effort.

体面的文档很重要。我不预期需要做任何太奇怪的事情，但你永远不知道。

Decent documentation is important. I don't anticipate needing to do anything too unusual with it, but you never know.

我们使用C ++， 。

We're using C++, and would like to work with a well-designed object-oriented architecture, if possible.

跨平台是必须的，良好的性能将有助于长期（我们可能会结束

Cross-platform is a must, and good performance would be helpful in the long run (we may end up porting to mobile platforms).

在作出决定之前，我需要考虑哪些因素？有没有人曾经与WebKit或Gecko之前？

Are there any considerations I need to take into account before making a decision? Has anyone worked with WebKit or Gecko before? If so, are there any articles or tutorials I might find useful?

更新：

感谢您的回应家伙。我们最终用Qt 4.5，其中包括WebKit。我们真的很高兴到目前为止，事实上我认为Qt可能是最好的UI框架，我曾经使用过;与本地Win32 API的编码的区别，这是令人吃惊的。

Thanks for the responses guys. We ended up going with Qt 4.5, which includes WebKit. We're really pleased with it so far, in fact I think Qt is probably the best UI framework I've ever used; the difference between coding with the native Win32 APIs and this is staggering. It's also real easy to learn, the only major issue we had was getting used to the signals/slots paradigm.

推荐答案

有一点点历史可能有助于你的决定。当苹果考虑使用哪个引擎在Safari中使用它们看看Gecko，但决定去与KHTML，叉并称为WebKit。他们这样做的原因是Gecko有很多遗留的垃圾仍然留在Netscape，并且复杂得多。

A little history might help in your decision. When Apple was considering which engine to use in making Safari they looked at Gecko, but decided to go with KHTML, fork it and called it WebKit. Their reasons for doing this was that Gecko had tons of legacy cruft still leftover from Netscape and was far more complicated.

KHTML / WebKit是新的，因此有更少的遗产。

KHTML/WebKit was newer, and thus had less legacy. It was also cleaner, quicker, and better documented.

Firefox 3的目标之一是清除代码库并简化它。从我听说他们做到了这一点，但我不知道如何比较当前的迭代WebKit。这显然不足以让谷歌成为Chrome，他们在Firefox上拥有大量股份。

One of the goals of Firefox 3 was to clean up the codebase and simplify it. From what I've heard they did do this, but I don't know how it compares with current iterations of WebKit. It apparently wasn't enough for Google when they made Chrome, and they have a significant stake in Firefox.

请参阅此处了解详情。

这篇关于什么是最好的HTML渲染引擎嵌入到应用程序中？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！