Qt替代？ （仅限窗口） [英] Qt alternative? (windows only)

问题描述

我使用Qt / C ++开发了一个客户端应用程序。最近，他们回来问我是否可以重新实现没有Qt的整个事情。所以我正在寻找一个替代Qt工具包。我需要的是良好的ActiveX处理，因为原始软件依赖于特定的ActiveX控件，我打算再次使用。我想坚持使用C ++（无.NET）。

I've developed an application to a client with Qt/C++. Recently they came back to me asking if I could reimplement the whole thing without Qt. So I'm looking for an alternative to Qt toolkit. What I need is good ActiveX handling because the original software depends on a particular ActiveX control which I intend to use again. I want to stick with C++ (no .NET).

有任何建议吗？

提前感谢。

推荐答案

MFC， WTL 和 wxWidgets 是Windows上的C ++ GUI工具包的三个主要选择。

MFC, WTL, and wxWidgets are your three primary choices for C++ GUI toolkits on Windows.

我不会怪客户端关闭Qt。我拒绝将它用于我的任何项目，以及。它无法复制本机控件和小部件是一个真正的问题;事情看起来在Windows上几乎可以接受，但一切在Mac OS X上完全崩溃。如果没有真正（或有用）跨平台，使用跨平台GUI库似乎没有什么意义。

I don't much blame the client for dismissing Qt. I refuse to use it for any of my projects, as well. Its inability to replicate the native controls and widgets is a real problem; things look mostly acceptable on Windows, but everything completely falls apart on Mac OS X. There seems little point in using a "cross-platform GUI library" if it isn't truly (or usefully) cross-platform.

我喜欢 MFC。显然，这是一个不受欢迎的意见，但大多数不喜欢MFC的人是同一个人，不理解Windows API。它是一个非常薄的抽象层，但它是一个非常有用的一个直接在Win32级别做任何事情。如果你要使用它，我可以推荐的最好的事情是变得完全熟悉Win32 API。类似的建议适用于WTL和wxWidgets。当然，好处是你的应用程序实际上看起来像一个本机应用程序。客户喜欢这样;它最大限度地减少了意外的行为，并帮助他们更容易地学习新的程序。

I like MFC. Apparently that's an unpopular opinion, but most of the people who dislike MFC are the same people who don't understand the Windows API. It's a very thin layer of abstraction, but it's a very useful one compared to doing everything directly at the Win32 level. If you're going to use it, the best thing I can recommend is becoming thoroughly familiar with the Win32 API. Similar advice applies to WTL and wxWidgets. The benefit, of course, is that your app will actually look and feel like a native application. Customers like that; it minimizes unexpected behavior and helps them learn new programs more easily.

MFC的最大的缺点是，它是一个相当大的库，增加了一个相当大的依赖关系到你的代码。可笑，当然，比巨兽是Qt，但重要如果相比直线WinAPI代码。 WTL是一个很好的选择，如果这是一个关注。这是一个更简单的包装Win32 API，提供了许多MFC的优点（任何人都可以说 CString ？），没有大多数的cruft和批量。再次，如果你不知道底层的API，使用痛苦，因为它甚至不是一个完整的抽象，但这是有助于保持轻盈。不幸的是，它在另一个意义上也很轻：文档。总之，没有什么，所以不浪费很多时间看。对我来说，这使MFC处于领先地位，因为它不仅是微软，而且还有其他人通过网络上容易找到的示例代码。

The biggest drawback of MFC is that it's a pretty hefty library that adds a sizable dependency to your code. Laughable, of course, compared to the behemoth that is Qt, but significant if compared to straight WinAPI code. WTL is a good alternative, if that's a concern. It's an even lighter wrapper over the Win32 API that provides a lot of the advantages of MFC (can anyone say CString?), without most of the cruft and bulk. Again, painful to use if you don't know the underlying API, as it's not even intended to be a complete abstraction, but that's what helps keep it light. Unfortunately, it's also light in another sense: documentation. In short, there isn't any, so don't waste much time looking. For me, that puts MFC in the lead, as it's quite well-documented, not only by Microsoft, but also by others through sample code easily found across the web.

很难提供任何更好的建议，而不知道你认为是什么meh关于MFC，相比Qt。 .NET Framework不是这样的meh;它有很多的whiz-bang功能，但也有很多缺点，乘车来。

It's difficult to provide any better recommendations without knowing what you think is "meh" about MFC, compared to Qt. The .NET Framework is not so "meh"; it's got a lot of whiz-bang features, but there are also a lot of drawbacks that come along for the ride.

这篇关于Qt替代？ （仅限窗口）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！