I am working with scientific software. We need to handle large data and have the fastest computation possible. This heavily restricts the use of programming languages. Legacy code also plays a role: the simulation code is a mixture of Fortran, C, and C++ (very little C++ in newer components). I would say, C++ is quite important because you'll reach for faster algorithms from the standard library (e.g. std::map instead of a linear search through an array). Our corresponding GUI application is written in C++. I have been part of porting it from wxWidgets to Qt. The main reasons (back at the time at least): 1) Better layouting that works with HiDPI screens. 2) Stylesheets to make a dark mode version (before Windows had dark mode). 3) Much better documentation. The free lunch is mostly over. Single core performance is not increasing by much. And computers nowadays are so fast that all applications should be really snappy. There is a "Better Software Conference" that talks about this kind of software. I'm totally in that camp. For cross platform development there is currently nothing better (to my knowledge) than Qt. I have yet to see an imGUI application that respects my display scaling (everything is really tiny). On the other hand, Qt is quite dated in its design. I guess we need to wait for reflection in future standards to see some changes (unfortunately, C++26 has been delayed). Still, there is nothing better available. Electron is never a good alternative for our use case because the overhead is too big. We are still using QWidgets. But that is mostly for legacy reasons. It seems to me that QML is also quite fast today and thus a viable alternative. If you have a dedicated designer for your software, you should probably go with QML. At our company we don't use any coding agents (but may ask dedicated questions to AI without revealing the actual code). Even though you can select not to make your code available for training, there is no guarantee that it won't be used. The risk is then that our only competitor might accidentally "steal" our code through use of AI. Even local models now seem to talk to the cloud, so that even in this case your code is not safe. And local models might still be too small to be really useful (and appropriate hardware is expensive). With the advent of AI reverse engineering I am not sure if there is any advantage of not (possibly) sharing your code with AI, if it can just extract the logic from the final executable. The question is also if you can't just move a lot faster that potential losses because of AI stealing your work for a competitor is offset. What should you do today? Everyone is now able to write crappy clones of existing software. Have a look at PhotoCraft: I guess it is quite easy to get the first 80% working. But, it will be really hard to get the last 20% working correctly and fast. One of the biggest problems (currently) is that AI will not respect the DRY principle. Bugs will be multiplied easily, but only be fixed in a single place. Also, with the goal to get "correct" software, AI sometimes likes to cheat by adapting the test cases to get all tests to pass (instead of fixing the code). With PhotoCraft and the likes this means that AI written software needs to be provided free of charge (that's the user expectation). Because otherwise somebody else will make an AI clone free of charge. This is not a sustainable buisiness model. I also expect that AI will only be able to basically write clones (or remix existing software). It cannot invent something new. So, if you want to earn money, you have to come up with a new idea and develop entirely new algorithms for your product. You can stand out from the crowd if your software is always snappy and responsive, uses a lot less than half a GB of disk space, and uses a lot less RAM. You might have to hand code these kinds of applications. You might know the AI 'jokes' of "and make no mistakes" and I forgot to say "make it safe" and "no bugs". What do you expect AI to do? It was trained on all available source code which might mean that it represents the average programmer. You should strive to become an above-average programmer which means you cannot use AI to write above-average code. To me, that is the only selling point (as in: it's the only way to actually make money) if your software is much better than AI-written software. Because users will expect AI software to be basically free (they could've done it themselves). Legacy software will always be treated differently and make different choices than an entirely new software project.

Colleagues, we are pleased to announce the release of QtitanComponents 2026.3, the latest update to its suite of professional UI components for the Qt framework. This release features major updates across core modules, including QtitanDataGrid 10, QtitanRibbon 8, QtitanNavigationUIDesign 5, QtitanDocking 6, and QtitanChart 8. The key highlight of this release is a complete evolution of the UI styling workflow driven by the company's proprietary DC Studio Tool. Developer Machines has shifted away from manual UI coding, moving to a fully automated design-to-code pipeline. As a direct result, QtitanComponents 2026.3 introduces the Microsoft 365 Style with Dark and Light palettes, built strictly on the Windows Fluent Kit 2 guidelines. The style is designed entirely in Figma and exported to Qt using the DC make utility (included in DC Studio Tool), which converts Figma documents into XML/FastInfoset stream containing all necessary primitives, images, states, and metrics. This ensures flawless High-DPI (HDPI) support, even on older versions of Qt 5. Core Component & Architecture Improvements In addition to the new styling workflow, version 2026.3 brings significant stability improvements, bug fixes, and deep architectural refactoring: Microsoft 365 Style Capabilities: We have added full animation support for key UI elements to deliver a fluid and modern user experience. Smooth transitions and dynamic animations are now integrated into buttons, icons, tabs, table columns, and other core controls. The new Microsoft 365 style responds perfectly to QPalette::Accent color changes. Simply update it for the entire application, and all checkboxes, radio buttons, input highlights, and other UI elements will instantly shift to match your new accent color. QtitanDataGrid 10: The mechanism for embedding native QWidgets into grid cells has been completely re-engineered. The legacy Qtitan::BackstageWidget class - which relied on private Qt headers and frequently broke between Qt versions - has been completely decoupled from the grid architecture. QtitanRibbon 8: The Ribbon customization mechanism and its dialog have been significantly upgraded, including the addition of a highly requested Apply button. Performance and reliability of the Qtitan::RibbonSystemMenu have also been improved. Windows Platform Enhancements: The implementation of Acrylic and Mica effects has been completely rewritten. We have stopped using the WinRT layer in favor of pure native WinAPI. This removes the previous WinRT limitations that blocked internal Qt mechanisms for OpenGL and QRhi rendering. Extended Compatibility: This release officially introduces full support for Qt 6.12.0, along with numerous under-the-hood stability fixes. [image: ms365style.png] Download trial - https://www.devmachines.com/download-for-qt.html Best regards, DevMachines Team https://www.devmachines.com

Thanks a lot for all this information. It has helped me get clarity on the questions that have been bugging me for weeks. I can now decide better what I want to do, and why. I will definitely share these with them ideas about unifying the UI for mobile and desktop with Qt, as it seems like it doesn't necessarily warrant replacing starting their application from scratch, only their UI code will get replaced (and its bindings).

This had been reported to Squish technical support team, and closed on behalf of the reporter. Unfortunately it was not possible to identify a clear cause so far.

[image: 01776ece-1308-4e3c-98fd-2749b3a4e221.png] Challenges faced: So when it came to building the d-pad, I was absolutely lost and was trying to approach this problem by drawing and arc instead and so I was reading about PathArc, and so it was getting so complicated, then I did see how it was implemented in the solution. repo: https://github.com/Meehir5907/QML-for-Beginners-Challenges/tree/Intro-Qt-Quick-My-Sol/StartingProject

@VikMorroHun said in blocked: cmake: command not found: In Linux I got more than 6000 hits How did you search to get 6000 hits?

10月28日（周三）下午三点，CSDN官网将直播《把 Qt 应用带到鸿蒙：Qt 6.12 for HarmonyOS 上手实战》网络研讨会。Qt研发主管齐亮将演示如何下载与安装、编译 Qt Widgets 与 Qt Quick 示例以及部署并在鸿蒙设备上运行。 [image: 5720445d-d9d8-43ab-894a-b84805898b31.jpg] 点击下面链接报名参会并提交你关心的问题，有机会赢取小礼物。 https://marketing.csdn.net/questions/Q2610151238528151630?shareId=2944&channel=8823488

Unless I misunderstand, this topic was written when this forum used Textile, which explains why some of the above have broken formatting. This question is therefore no longer relevant for this forum. That being said, to anwer this question should anyone else land on this topic from a search engine, this should (now?) be possible. 🅭🄍