Well, I am old enough that I am using Qt Creator because it was the only good cross platform IDE (VS Code didn't exist, yet). I still very much like the simplicity of Qt Creator. Since modern Qt projects are always CMake-based those projects can be used with any IDE. This also means that the IDE has nothing to do with finding other libraries as this is fully in the domain of CMake. The same is true for compilation times as CMake (hopefully through ninja) is compiling your project, the choice of IDE does not matter. Qt Creator certainly has the best integration of the Qt documentation as you can easily switch there and search. Your operating system should also play a part in choosing an IDE. I tend to still use Qt Creator on Windows. However, the debugger is really slow on Windows. Our projects are still qmake-based and so I generate a VS project and open that one with Visual Studio (not Code!). This should be doable with a CMake project directly, but in our experience it is quite slow to switch between release and debug. Otherwise VS is also a solid choice. As I am still using QtWidgets I also still need the Qt Designer. This is yet another point for Qt Creator as it is directly integrated. Every IDE will provide basic code completion. From my experience (not a Qt project, though) CLion has a much more advanced code completion as it will (mostly correctly) predict the next line of code if you are writing some boilerplate. I am not sure how much AI will help with learning Qt inside an IDE. Especially, as it might mix Qt 4, 5, and 6. But, you'll certainly get AI coding integration with any IDE.

Hi Priyanka, I'm delighted to see that PlugFrame is generating interest within the technical community. To briefly answer your questions, I drew inspiration from some of the core concepts of the OSGi architecture when designing PlugFrame. Currently, the first version allows bundles to declare their services to the system at startup. Consumer bundles retrieve services from the framework through a service registry mechanism (they obtain a reference to the framework service during initialization). Bundles also define a startup level, and the framework uses an incremental startup procedure. For now, dependencies are managed by the developer at design time. In future versions, I would like dependencies to be resolved dynamically through a dedicated dependency resolution mechanism. However, these features are lower priority at the moment, as my current focus is to move OpLink toward a production-ready state. Since I am currently the sole developer and funder of the project, any contribution, feedback, or sponsorship would be greatly appreciated. Best regards, Christophe

[image: b6c267c8-8af6-4e1b-b44f-4e891e9c2656.png] 哥哥姐姐们，这个带搜索功能的帮助界面怎么恢复啊？ How can I restore this help interface with search function?

I recommend to contact technical support regarding this. However, the Floating License Server (FLS) is being superseded by the Qt License Server (QLS). And the general plan is to phase out use of FLS over time. So going forward, it is best to check the respective API of QLS instead. https://doc.qt.io/qtlicenseserver/qls-overview.html https://doc.qt.io/qtlicenseserver/qls-restapi.html

@Anuj-Srivastava Are you sure you posted in the right sub-forum?

With change 733351 in Qt Gerrit now merged into the dev branch of qtbase, along with several other changes merged into the qt5 dev branch (see the harmonyos_upstream topic), qtbase dev now supports building on HarmonyOS 6.0.0 (API Level 20). If you are interested in building qtbase for HarmonyOS, please refer to the Qt Wiki page.

Normalerweise, in das build Verzeichnis (ich bin nicht was das richtige Wort für "folder" ist).

Hi, Akismet can be sensitive sometimes. What exactly did you want to add to your post ? I have not understood.