Qt vs wxWidgets [Closed]
The Question Has Been Asked Before, but the Most Recent One Seems to Be from Two Year's Ago, So There Must Be New Developments That Must Have Occurred in the...
![Qt vs wxWidgets [Closed]](https://www.alledaags.nl/uploads/qt-vs-wxwidgets-closed_1200.jpg)
The question has been asked before, but the most recent one seems to be from two years ago, so there must be new developments that must have occurred in the two toolkits.
So which toolkit should I use for developing a GUI with C++? What are the pros/cons of each?
2 Answers
In my obviously biased opinion, the advantages of wxWidgets are:
- Native widgets (as far as possible) guarantee native look and feel
- Standard C++ only, no special preprocessor/extensions
- Possible to link statically to closed source applications without buying a commercial licence
Also, whether it's an advantage or a disadvantage is up to you to decide, but wxWidgets is primarily a GUI library and seeks to play well with the other specialized libraries (like SOCI or asio, for database and network support, respectively) instead of trying to be the one and only true library for everything.
If you are comparing wxWidgets with Qt, wxWidgets literally stands no where. Qt is a complete framework where you can write code and generate GUI for Linux, Windows, MAC, Android, IOS and even blackberry, and other embedded systems. It has classes for almost anything you wish to do, from controlling your webcam to bluetooth devices etc. Unless you are doing something very specific, you won't need any 3rd party library.
On the other hand, wxWidgets, essentially offers a way of creating GUI, with many other classes too but they are quite few in comparison to Qt.
Sarah Jenkins is a veteran tech journalist with over 12 years of experience covering artificial intelligence, mobile innovations, and digital ethics. Her insights have appeared in leading technology publications worldwide.
