Hi, If you write your algo into Javascript or you can edit it, you are so doing Qml wrong! leave your algo into C++ please, your model/controler too shall be be C++. Qml is for the GUI layer only, it so simple it is temping to add more logic into it, but that's an error that will bit you in the long run. You can compile Qml and with Qt6 convert Qml to C++, so I wonder what would be more a problem, do you ship any library into your software or you do static compiling of everything so nobody can inspect your lib? Cause, exposing API from a lib or any other languages is not hard to reverse used in any way. You do not protect code by obfuscation, but protect code with your license. Javascript engine was just a practical way at the time, probably a new engine will come one day, there is some Qml without Javascript engine coming into Qt6 paving the way for it.
Qml, is just a widgets rendering way to declare the GUI in a much simpler and cleaner way. If you want to stick to QWidgets, please do, there is no shame into QWidgets, he just have a limited future for expansion. The multiple rendering engine the embedded and Qt/Qml lite will be more then welcome for me. I have switch to Qml and could easily range it from big 3D CAD medical software, mobile tools and some development on embedded device. I haven't any issue and could reuse code for that whole range (both Qml and C++). Nothing in the world will make you change your idea, I known that and I do not expect anything to change from you. IMO your are stuck in the past, but if you like so much those old version, I'm sure they are still working just like they did back then, nobody force anybody to use the latest version as far as I can see, Qt4 is still useable if you truly want to keep it that way. Break into API happen for a good reason, to remove bad API or to allow better possibility. If you have never rewrite any part of the code to allow better architecture to take place you must be a coding god that can write code flawless or something must horrible into those API. Needs and requirements evolved, code need to evolve with them. I for one, really enjoy Qml and the Qt Meta, wish I could get ride of the Moc, but this will wait until C++ get more reflexion built-in. QWidgets, ditch it and never been more happy since then, I had to maintain a few applications, it now feel cumbersome when I touch them. This only reflect my own opion, sorry for all the noise to other users, Jerome -----Original Message----- From: Interest <interest-boun...@qt-project.org> On Behalf Of Roland Hughes Sent: July 13, 2020 8:31 AM To: interest@qt-project.org; rjvber...@gmail.com; Donald Carr <sirsp...@gmail.com> Subject: Re: [Interest] rebooted QtWebKit for Qt4?? On 7/13/20 5:00 AM, interest-requ...@qt-project.org wrote: > I also didn't complain about stability, but coming from fundamental research > I can relate to the feeling that API breakage of the type Qt3 -> Qt4 -> Qt5 > (and who knows what Qt6 has in stock) happens too fast, too soon. Kittens swatting at bright shiny objects. Let us not forget that QML+JavaScript is completely insecure in the OpenSource world. All of that JavaScript gets stuffed into the binary you ship as free text. Anyone with a decent text editor can read/extract your super secret proprietary algorithms. Worse yet, anyone with enough patience can change a binary in the field. -- Roland Hughes, President Logikal Solutions (630)-205-1593 http://www.theminimumyouneedtoknow.com http://www.infiniteexposure.net http://www.johnsmith-book.com http://www.logikalblog.com http://www.interestingauthors.com/blog _______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest _______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
