On Saturday 02 January 2016 19:00:48 René J.V. Bertin wrote: > > I very much disagree with this approach. Qt is opensource, if there's > > something to be fixed in QProcess, make a patch, > > then it won't be hypothetical. I don't see "starting a GUI application" as > > a KF5-specific need at all. > > You saw I said "wait for QProcess to be improved", right? I don't expect a > patch for QProcess to be incorporated before 5.7.x ...
Patience is a virtue :-) > Ok, so what about the requirements on QProcess? Anything beyond what's > possible with QProcess::startDetached and possibly launch confirmation? > Should QProcess figure out transparently (or rather, opaquely :)) whether to > use LaunchServices or not, or should the developer be given a way to override > it, or even switch to switch to LaunchServices rather than using standard > Posix APIs? Those are implementation details. IMHO the API shouldn't talk about any of that, but rather have a flag like "it's a GUI app that I'm starting", which would hint at using LaunchServices on OSX is that's the only way to bring it to the front. -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE Frameworks 5 _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
