1

Topic: Qt Widgets vs. Qt Quick

Good afternoon, it is necessary to write  the program with support of various platforms. Stopped on Qt. Here write that for such purposes it is better to use Widgets though it is possible and to use Qt Quick 2. Looking what rates there is development Qt Quick 2, there is a question, and can cost all the same to look in this side? It would be desirable to put money on the correct horse and in five years it not to appear at the broken trough. Thanks.

2

Re: Qt Widgets vs. Qt Quick

Hello, Iso12, you wrote: I> Good afternoon, I> it is necessary to write  the program with support of various platforms. Stopped on Qt. I>... I> Thanks. And it is possible more in detail about what should be able GUI programs? If there are no requirements to super high dpi, to difficult smooth animations, is strong  to interfaces, etc. take widgets. Mature and stable technology, the good documentation, examples and  (that you will not tell about QtQuick). Technically to debug much easier. Examples of programs on : ICQ, Telegram. QtQuick now very actively develops. While under desktops there is distinct support of windows everyone dock and some other  no tinsel. Besides - writing of the code demands hardly the big skills. It is necessary to be able to divide without fanaticism GUI and to the logician, there is more difficult debugging QML. Pure GUI on QtQuick I straight off will not remember. I can tell that Blizzard launcher  a compound  and QML.

3

Re: Qt Widgets vs. Qt Quick

Hello, SaZ, you wrote: SaZ> And it is possible more in detail about what should be able GUI programs? The program should be able: to read out (and to write) the information from files to transfer and obtain the data through TCP/IP a socket to display the information for editing to draw the chart unit to send the data on the press to create pdf files.

4

Re: Qt Widgets vs. Qt Quick

Hello, SaZ, you wrote: SaZ> If there are requirements to super high dpi At  no problem with it?

5

Re: Qt Widgets vs. Qt Quick

Hello, Amygdala, you wrote: SaZ>> If there are requirements to super high dpi A> At  no problem with it? Well it not absolutely a problem . It is a problem practically any GUI on many desktops (everyones UWP it is not counted). Simply  practically always c and  on CPU (except for some direct calls of type DrawFrameControl, but here I am not assured).  any difficult scenes even at FullHD already begin  CPU time. Once it was necessary to refuse from QGraphicsScene in favor of QQuickWidget and implementation of this specific scene on QML. QtQuick it is drawn with  on GPU and in a separate flow. And all it from a box.

6

Re: Qt Widgets vs. Qt Quick

Hello, Iso12, you wrote: I> Hello, SaZ, you wrote: SaZ>> And it is possible more in detail about what should be able GUI programs? I> the program should be able: I> I> to read out (and to write) the information from files, I> to transfer and obtain the data through TCP/IP a socket, I> to display the information for editing, I> to draw the chart unit, I> to send the data on the press, I> to create pdf files. I> it is enough my answer (including comments in this branch)? If charts not difficult - take . And if in advance make normal architecture and separate logic of application from GUI there will be no problems with migration on other technologies.

7

Re: Qt Widgets vs. Qt Quick

Hello, Iso12, you wrote: SaZ>> And it is possible more in detail about what should be able GUI programs? I> the program should be able: I> to read out (and to write) the information from files, Not GUI I> to transfer and obtain the data through TCP/IP a socket, Not GUI I> to display the information for editing, Normal TextEdit, or it is necessary that that such Is an example on QWidgets I> to draw the chart unit, And here it is possible to select, do most either QML qtcharts or QWidgtes qwt I> to send the data on the press, QPrinter I> to create pdf files. Looking what, can will enough QPrinter or it is necessary to drag NCReport To that that wrote SaZ I will add: At qml there is plus, the interface is written faster.

8

Re: Qt Widgets vs. Qt Quick

Hello, Igore, you wrote: I> At qml there is plus, the interface is written faster. Too in pluses QML I will add that various configurations and bindings become elementarily and very quickly. Animations in pair lines . However, one of principal problems QML that here works, there does not work, and here fish wrapped. Dampish it.

9

Re: Qt Widgets vs. Qt Quick

Hello, Iso12, you wrote: SaZ>> And it is possible more in detail about what should be able GUI programs? I> the program should be able: I> I> to read out (and to write) the information from files, I> to transfer and obtain the data through TCP/IP a socket, I> to display the information for editing, I> to draw the chart unit, I> to send the data on the press, I> to create pdf files. I> all tasks behind an exception "to draw the chart unit" and "to display the information for editing" are orthogonal GUI. If the mouse and the keypad is more preferable to the remained two tasks - that QtWidgets, if touch the interface - that QtQuick. And generally QtQuick and QtWidgets if needed it is possible to hinder without special problems.