Qt Creator Tutorial – QTcpSocket & QTcpServer
Thanks for this. Anjuta looks pretty much like what I’ve been looking for. I’m going to play around with it a bit. If it’s not right, I’ll look at QT. I’m surprised that both GTK and QT achieve the same end result, I guess it’s just a matter of preference.
@Nootrino: you have to remember that in the FLOSS world, there is often more than one established solution. The reason many people have chosen, one or the other, is based on their C vs, C++ position. Of course, licensing played a bigger role in the past. Regardless of the fact that other frameworks exist in many languages, it is generally more in agreement with one method.
Qt is mainly used in KDE and GTK+ in GNOME. So, if you want to develop for GNOME, consider GTK+ since the necessary dependencies for the GTK+ libraries should already be installed on a GNOME system; the end user will not need to install them. GTK+ development also benefits from a tool called Glade Interface Designer; if you wish, you can use that to create your user interfaces.
Qt Creator Tutorial – QListWidget
Qt is much more than just a cross-platform SDK – it’s a technology strategy that lets you quickly and cost-effectively design, develop, deploy, and maintain software while delivering a seamless user experience across all devices.
Qt is written in C++ and, therefore, we need to access it using bindings or bridges (I haven’t found a better word for bindings) that allow us to communicate our Python code with Qt code written in C++.
5.6.x.PySide2CPython2 ≥ 2.7, CPython3 ≥ 3.5Qt ≥ 5.6YesGPL, LGPL or commercialThe project is also known as “Qt for Python”. PySide2 releases keep pace with Qt5 releases. The best way to stay up to date is to follow their blog.
In this course I will be using QtPy, developed by the folks at Spyder-IDE. So, any version of PyQt5 or PySide2 should work for you. In the previous chapter we installed a virtual environment where both the PyQt5 and PySide2 libraries were installed.
Qt Creator Tutorial – QString
Qt has all its core modules, add-on modules and the Qt Creator IDE available for both commercial and GPL licensed versions. However, there are some add-on modules that are not available for LGPL licenses.
The most significant feature of this type of licensing is that you don’t have to pay anything, however some limitations are set. Both types of open source licenses have several differences that are important.
The commercial license is my recommendation when it comes to professional projects. With it you pay for professional support, which can be vital when there are deadlines to meet, and also for intellectual property indemnification, which means you don’t have to worry about who owns all the code you are using, since you bought the rights to it in a commercial transaction and therefore the vendor is responsible.
With the commercial license you can use Qt however you want. This means statically or didactically compiling Qt libraries, modifying them without distributing your modifications, as well as keeping your application code closed.
Qt Creator Tutorial – QTableWidget
If you had the difference of venturing into Delphi land or Qt land, which one would you choose? I know they are not totally comparable. For my part, I have experience in Windows development with Builder C++ (almost Delphi) and MFC (almost Qt), with a little more time working with Builder C++. Remove the cross-platform capability of Qt in your analysis.
If you are talking about UI frameworks, then you should compare Qt to the VCL, not the IDE (Delphi in this case). I know I’m being a fanboy, but Delphi is the IDE, Object-Pascal is the language and VCL is the graphics framework.
C++ is a disadvantage, e.g. compile times, packaging and a less integrated IDE. However, Qt makes C++ feel more like a higher-level language. QStrings takes all the pain out of string handling, for example. Therefore, the additional problems with C++ that I would normally face, e.g. more buggy code, are less frequent in my experience when using Qt.
Also, there are more libraries for Delphi than for Qt, but this is mitigated by the fact that you can only use the ac or c ++ library in a Qt project, and also because Qt has all the features you often don’t have to look further.