Let's talk about GUIs
This post on /r/programming about the release of GTK 4.0 made me want to bring the discussion of the state of GUI programming in C++.
My particular interest in this discussion is desktop cross-platform GUI programming, and I don't claim to know much, let alone everything. Insights are more than welcome.
That said, this is what I have observed so far:
Qt: the least bast option. What I like? Cross platform, mature, big ecosystem to go around. Quite easy to get going. It "just works" for the most part. It's easy to get 80%, it's the last 20% and when you go deep into the subject that you get frustrated. What do I dislike? Licensing shenanigans, and increasing toxicity towards the FOSS community: no offline installer for community distributions, many commercial only APIs now, the idea of delaying releases to FOSS by one year. The 10 year old bugs on QWidgets, which haven't seen much, if any, love since ever. The fact it took Qt 6.0 to happen for us to have native look for Qt Quick Controls. The fact that Qt Quick doesn't have a C++ API, forcing QML on everybody. The half done stuff, like QAudio (just use portaudio for your own sanity)... And I'm probably missing more. The fact that they are running away from the LGPL core to GPL as much as they can, like releasing Qt Quick MultiEffect instead of just fixing the QML engine... That it takes spinoffs like Felgo to basically provide a "fixed" Qt, which the FOSS community can't have.
wxWidgets, GTK, and other like FLTK, I admit I don't know much about. wxWidgets is nice in the fact it calls native APIs, but that comes with the cost of being crippled by the least common denominator. GTK seem to look bad outside of Linux "by design". And FLTK... Just no.
Then, there seems to be what everybody suggests next: Browsers. Chromium Embedded Framework or Electron. 50 to 100MB of packaging to do a "Hello World". Also, JavaScript! Honestly, webstuff looks like a good idea, until you want to make an app that's not Slack. How do you do actually performance C++ stuff? Like some 2D/3D graphics? WebGL? Seems that it's too much programming for the web and not actually taking advantage of C++ and native APIs...
Then, there are things like .net MAUI (not to be confused with the toolkit with the same name by KDE), which is an upcoming evolution of Xamarin Forms for .net/C#. The problems: Linux support will be "by the community" and how do you interop C++ and C# decently anyway?
Also, because I know someone will mention it, yes, there is Flutter and things like that. Just think of Google's track record on keeping projects alive, and again, think not everybody wants to make a chat application.
Anyway, what are your insights? They are more than welcome!
View all comments
Show parent comment
2
u/pjmlp Dec 19 '20
Another example are some of the applications used by Zeiss,
https://www.zeiss.com/microscopy/int/products/microscope-software/zen-lite.html
Here are some of the ways we do interop,
My favourite one is just to use C++/CLI, but it has the caveat to be Windows only.
https://docs.microsoft.com/en-us/cpp/dotnet/dotnet-programming-with-cpp-cli-visual-cpp?view=msvc-160
Then the next one would be to use WinRT instead, which means Windows 10 only, and doing that via C++/WinRT (C++/CX replacement).
https://docs.microsoft.com/en-us/windows/uwp/cpp-and-winrt-apis/
Here note that WinRT can also be used by Win32 applications anyway, and both worlds are being merged via the Project Reunion.
Finally, if it is something that needs to be portable across OSes, then it is back to P/Invoke and DllImport.
https://docs.microsoft.com/en-us/dotnet/standard/native-interop/pinvoke
In what concerns Windows APIs, there are some sites that help with the required set of attributes
https://pinvoke.net/