This video as well as the open source code base are the most comprehensive learning resource on Qt yet (Alongside Ventilator project by ICS). Thank you for developing this code base in the open. A big hug and thanks a lot.
Now comes the question: does the use of a lot of QML bindings lead to lower performance? I ask this because when trying Scrite 2 months ago on a mac, I noticed that it hang for a few seconds a couple of times during light usage. Is this just me? If not, Is this a deep architectural issue (too many bindings and events), or something that can improve with optimisations over time.
Thanks @Satyam Tiwary for your kind words. Regarding your question: The UI freezes were more to do the way in which classes in the business logic layers were implemented. For instance in Scrite, each scene is rendered using a TextEdit QML component on the Screenplay Editor. The text shown in it is formatted to screenplay standards using a QSyntaxHighlighter implementation in C++, hooked to the QTextDocument in TextEdit. In addition to that, we show current page, time etc in the UI for which we have to pool in texts from across all scenes into a single "invisible" QTextDocument to compute page breaks, count etc. This means running the syntax highlighter and updating the "invisible" text document for each key-stroke, both of which are done using custom C++ code in Scrite. A few updates ago, the code which did this was not optimized which resulted in UI freezes. Recent updates should have gotten much much better. We would have probably run into this issue even if we had used widgets. We are spending a lot of time in 0.6 series optimizing various aspects of the code in an effort to make it faster. Moving time-consuming computations to threads, trying to batch update wherever possible to optimize repaints. So, short answer to your question is: performance is something we can improve over a period of time. We are sure Scrite 0.7 will be in a much better shape than 0.6. And a future 0.9 will be in a much much better shape than 0.7. At some point we plan to move to Qt 5.15.5 to leverage all the performance benefits the newer version of Qt will bring.
How to smooth scroll to an item position in QML ListView ? As of now i'm using positionViewAtIndex(), this does not do the smooth scroll animation. I'm new to QML, any ideas about how to implement it ?
@Zakaria: Thank you for your kind words. Regarding tutorials on QML & Qt Quick, we have benefited a lot from KDAB's video series on QML. Sharing the link below. th-cam.com/play/PL6CJYn40gN6hdNC1IGQZfVI707dh9DPRc.html
Yes, you can build mobile & browser apps using QML. Infact we plan make mobile and web-versions of Scrite once we are past version 1.0. We have a few more things to complete before we can call it a 1.0 release, hopefully from later this year we can start working on the mobile and web apps. See Also: doc.qt.io/qt-5/wasm.html
Yes, surely. You won't get native looking apps using QML as yet - not without some effort atleast. And if you want really good graphics and animation, you have to insist on using the dedicated graphics card in the Info.plist (NSSupportsAutomaticGraphicsSwitching = false). But other than that I think you can write really good looking and well functioning apps using QML for macOS.
Hi Prasanth, I am currently working as a python automation tester, as my interest is mostly towards the development, I would like to change my job role into a developer, Can you please explain me the scope of my carrier, if I choose to go with Qt. What would be your suggestion?? Please help me with this, as I am very confused in shifting my role.
thats a great app, thanks for sharing QML tutorial
This video as well as the open source code base are the most comprehensive learning resource on Qt yet (Alongside Ventilator project by ICS). Thank you for developing this code base in the open. A big hug and thanks a lot.
Now comes the question: does the use of a lot of QML bindings lead to lower performance? I ask this because when trying Scrite 2 months ago on a mac, I noticed that it hang for a few seconds a couple of times during light usage. Is this just me? If not, Is this a deep architectural issue (too many bindings and events), or something that can improve with optimisations over time.
Thanks @Satyam Tiwary for your kind words.
Regarding your question: The UI freezes were more to do the way in which classes in the business logic layers were implemented. For instance in Scrite, each scene is rendered using a TextEdit QML component on the Screenplay Editor. The text shown in it is formatted to screenplay standards using a QSyntaxHighlighter implementation in C++, hooked to the QTextDocument in TextEdit. In addition to that, we show current page, time etc in the UI for which we have to pool in texts from across all scenes into a single "invisible" QTextDocument to compute page breaks, count etc. This means running the syntax highlighter and updating the "invisible" text document for each key-stroke, both of which are done using custom C++ code in Scrite. A few updates ago, the code which did this was not optimized which resulted in UI freezes. Recent updates should have gotten much much better. We would have probably run into this issue even if we had used widgets.
We are spending a lot of time in 0.6 series optimizing various aspects of the code in an effort to make it faster. Moving time-consuming computations to threads, trying to batch update wherever possible to optimize repaints.
So, short answer to your question is: performance is something we can improve over a period of time. We are sure Scrite 0.7 will be in a much better shape than 0.6. And a future 0.9 will be in a much much better shape than 0.7. At some point we plan to move to Qt 5.15.5 to leverage all the performance benefits the newer version of Qt will bring.
Thanks for this video . Great Explanation !
Very impressive work and great talk. I will try Scrite out when I am developing my movie.
Awesome, thank you!
Incredible!
How to smooth scroll to an item position in QML ListView ? As of now i'm using positionViewAtIndex(), this does not do the smooth scroll animation. I'm new to QML, any ideas about how to implement it ?
You're genius 💙
Thanks for sharing 💛
We want some tutorials about Qml Qt Quick
@Zakaria: Thank you for your kind words. Regarding tutorials on QML & Qt Quick, we have benefited a lot from KDAB's video series on QML. Sharing the link below.
th-cam.com/play/PL6CJYn40gN6hdNC1IGQZfVI707dh9DPRc.html
Excellent presentation! Is it also possible to share the Q&A from the QT Dev Days presentation?
Unfortunately, we don't have a recording of the QA session. At some point we hope that the Qt Company will post it on their channel(s).
Can you port this with PyQT for python?
I don't think we will be doing the port, since we are C++ devs.
Bonjour monsieur , merci pour ca .
On construit l'interface graphique avec du QML et toute la logique avec C++ , merci
Can i build a website, mobile application using QML....?
Yes, you can build mobile & browser apps using QML. Infact we plan make mobile and web-versions of Scrite once we are past version 1.0. We have a few more things to complete before we can call it a 1.0 release, hopefully from later this year we can start working on the mobile and web apps.
See Also: doc.qt.io/qt-5/wasm.html
Is it good for MacOS too ?
Yes, surely. You won't get native looking apps using QML as yet - not without some effort atleast. And if you want really good graphics and animation, you have to insist on using the dedicated graphics card in the Info.plist (NSSupportsAutomaticGraphicsSwitching = false). But other than that I think you can write really good looking and well functioning apps using QML for macOS.
Scrite works on macOS. Do take a look: www.scrite.io/index.php/download-macOS/
Hi Prasanth, I am currently working as a python automation tester, as my interest is mostly towards the development, I would like to change my job role into a developer, Can you please explain me the scope of my carrier, if I choose to go with Qt. What would be your suggestion?? Please help me with this, as I am very confused in shifting my role.