Hello, SaZ, you wrote: AG>> it is possible, the example mapviewer and is interesting, in the sense that there all from-box. SaZ> it is enough of it. To clear interest to the given subject - YES. To alter the considerable project - it is not assured As to the HARDWARE I gave it an alternative variant of a choice. SaZ> your minus is not clear and is not argued. The argumentation of that the decision on QML, is not unambiguously possible and unique choice, has been resulted by me above. Well and further, to take or not to take those or other decisions in the projects: everyone solves itself. AG>> nevertheless that confuses me: AG>> 1) the HARDWARE wrote that it interests on a C ++ (yes on pluses). In an example: in core JS and QML (is only main.cpp). SaZ> There are no problems in making all on pure pluses. It is not necessary to confuse QML, which language and QtQuick which changeover is. OK! Whether it means, what everything, what is made in an example mapviewer it is possible to implement on a C ++ (without the intermediate layer QML <-> CPP)? AG>> 2) About rendering on CPU: for sheaf QGraphicsView and QGraphicsScene there is rendering OpenGL on GPU. AG>> I Will remind that in that example, on I originally referred: http://doc.qt.io/qt-5/qtwidgets-graphic
ample.html - it is possible to apply rendering by means OpenGL. SaZ> And it is possible a specific example... In an example with chips on boards there is a line: graphicsView-> setViewport (openGlButton-> isChecked ()? new QGLWidget (QGLFormat (QGL:: SampleBuffers)): new QWidget); Unless not she answers, for rendering application through OpenGL? AG>> About ready components - them to take logical, if at you all on QtQuick. SaZ> Is not present, not logically. For desktop applications is a normal practice to use together with QtQuick. A good example - Blizzard Launcher. Searched in Google "Blizzard Launcher", found here it: https://github.com/Blizzard/qt is it? SaZ> What for you give all these links to me? Unless only you one read the given forum? I give references that all could trace train of thought AG>> P.S. If it is possible, dear companion SaZ, give a reference where criticize application of scenes on SaZ> For example here. Thanks, an interesting material! In it, truth, all is not too unambiguous (about an example with chips on boards): If you need to show the same scene multiple ways when migrating to Qt Quick, then you will need to separate the data you would like to visualize from the scene defined in QML. Populate each Qt Quick scene with only the data present in the view of your logical scene. This is more complicated but does provide more flexibility in how you store the state of your shared scene. I concede that it was easier to do in QGraphicsView. But at least - is over what to think. About speed of development - I will not argue, it is quite possible that QML allows to develop code GUI faster. Possibly, at writing of business logic for QML, the C ++ is more popular JS, than.