On Tuesday 7 May 2024 10:50:09 GMT-7 Lars Knoll via Development wrote: > There could also be use cases where you have split your app into two parts, > a UI running in one process and a backend running in another one. The > backend doesn’t link against any GUI libraries, but might need to launch an > OAuth flow in response to something that’s been triggered by the UI. And > there could be many reasons why you’d want a process separation, security > being one of them. > > So I do believe there are valid use cases for opening a browser window from > a process that does not link against a GUI library. Given that the > implementation doesn’t require anything UI specific neither I don’t see why > we shouldn’t have it in Qt Core.
I agree with the conclusion. But your premise is talking about it being a tightly-coupled UI and non-UI process components. So the non-UI component doesn't want to use QCoreDesktopServices::openUrl in the first place: it wants to communicate with its UI component through whichever communication mechanism it has established. -- Thiago Macieira - thiago.macieira (AT) intel.com Principal Engineer - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
-- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
