C++ & Qt

14 September 2025 08:28

qt despite beeing cross-platform, I think is more mobile (if ui is not very complicated)...

'webview' approach is the easiest for pc. any ui can be done with not a lot of effort
data sharing is fast, v8 is pre-jitted to pcode and jitted to native

size overhead may be a problem if you bundle everything, but if use webview — no problem

always use backend logic such as some arrays processing in c++ as callout

C++ & Qt

14 September 2025 08:21

unique id in app to see purchase leak will not work. attackers always buy your soft from malware infected user, etc

C++ & Qt

14 September 2025 08:19

if you pay for protectors eg. license managers — think that your app is broken after week and this version is free for people that don't want to buy it.... so you may monitor net and ask to delete those at the very beginning

C++ & Qt

14 September 2025 08:16

write the cleanest code possible, easiest to you as possible, keeping in mind that attacker knows it 100%, maybe even better then you. think of rsa,elipticccurve/aes

C++ & Qt

14 September 2025 07:54

yes, I completely agree that QML business model supports Qt Company, that is for sure a good thing. I think people need to know that if they make a commercial app and use QML, they may leak its code. They need to know how it is working, so they are more likely to pay for the commercial license

C++ & Qt

14 September 2025 07:52

Regardless, as someone that works for TQtC, but is also an open source advocate, I want Qt to be accessible to people, but we also have to pay the bills, so commercial right now is a necessity to advance the toolkit.

I think of folks are profiting off of their own code that uses Qt, they should give some back to the community in the form of some open code.

C++ & Qt

14 September 2025 07:49

resources is easy to extract anyway, you can encrypt those, but since with LGPL all libraries are separate, it is easy to inject library that extracts runtime QML code

C++ & Qt

14 September 2025 07:47

while using QWidgets you are 100% safe from leaking the code even with LGPL

C++ & Qt

14 September 2025 07:46

also qmlcachegen only improves startup by skipping QML parsing, while qmlsc boosts both startup and runtime by compiling QML/JS into native code, so we don’t get the best thing unless we pay

C++ & Qt

14 September 2025 07:43

QML precompiled with qmlcachegen can be decompiled to nearly original QML because it preserves bytecode and structure, while qmlsc (commercial) translates QML into C++/machine code and cannot be decompiled back into QML

C++ & Qt

14 September 2025 07:41

the compilation thing is a bit fuzzy, because I think there are 3 implementations of it.. One that came out long ago in Qt 5.7 I think it was.. That was discontinued in favor of newer better means of compilation... Those ones I think are commercial, but I'm not sure if both of them are.

C++ & Qt

14 September 2025 07:38

Qt Quick Compiler only shipped with Qt Commercial License, either your QML is easy to read, even if you put that to the app resources, equal to be open sourced

C++ & Qt

14 September 2025 07:36

for not commercial license QML code is forced to be open source

C++ & Qt

14 September 2025 00:16

What you might be remembering is that Qt Widgets was moved out of the QtGui module, into its own module. This happened in Qt 5 (? I think?) - QGuiApplication was created, so there was no dependence on Qt Widgets when you create a Qt QML application.

That was much longer than 3 years ago though.

C++ & Qt

14 September 2025 00:09

qml can be compiled to C++, but if it's got complex javascript, it won't use the cached C++ conversion.

C++ & Qt

14 September 2025 08:24

Hacking isn’t such a big problem because nothing can prevent it. Decompiling to original code is a bigger issue since that is easier for competitors to replicate your app.

C++ & Qt

14 September 2025 08:21

best way to protect is not to make your code part download at runtime ( — they will be dumped in no time and code coverage will be repeated, as env at start of app, including syscall's/rtdsc's) but to move the logic to your server. there's no other way

C++ & Qt

14 September 2025 08:17

if your app is good, pay what you need to make it great for use

C++ & Qt

14 September 2025 08:01

Is there anyone who works for Qt company here? I need some help and support ignoring me.

C++ & Qt

14 September 2025 07:53

QGraphicsView is so ancient though.

C++ & Qt

14 September 2025 07:51

QGraphicsView + OpenGL backend is the choice for GPU acceleration interface with no code leaking for free

C++ & Qt

14 September 2025 07:47

You can always compile your qml in as resources... but I suppose then qmlcachegen can't work on it..

C++ & Qt

14 September 2025 07:46

Ahh.. I see.
Because qmlcachegen still requires the qml, you're saying that it is inherently open source.

C++ & Qt

14 September 2025 07:43

that makes QML not the best choice for many of us unless we pay for the license

C++ & Qt

14 September 2025 07:41

I not said that license requires that, I meant that it will be open source out of your choice unless you pay for the commercial license

C++ & Qt

14 September 2025 07:40

There are actually several iterations of quick compilation.. I think you are right that the current iteration is commercial only. However, the blanket statement that any non-commercial QML application is required to be open sourced (GPLv3) is incorrect.

C++ & Qt

14 September 2025 07:37

Incorrect. Where are you getting that information from?

C++ & Qt

14 September 2025 07:35

commercial license only

C++ & Qt

14 September 2025 00:13

The recommendation for new UIs is to use QML, but widgets is not deprecated.
Widgets is not going away anytime soon. Too many applications / projects use it.

Widgets is not graphics accelerated — it uses the QPainter API, and that's not going to change.

QML uses the scene graph, which is backed by Qt RHI, which is a thin layer ontop of OpenGL, DirectX, Metal, and Vulkan — so QML will always be faster to render than Widgets.

C++ & Qt

14 September 2025 00:07

There's a huge difference between QML+JS, and bundling in the entirety of chromium/webengine... webengine is HUGE. QML+JS support is much smaller.