Windows 7+ desktop apps - what's the best UI toolkit for a new project?
Posted
by
Chris Adams
on Programmers
See other posts from Programmers
or by Chris Adams
Published on 2012-10-24T16:02:00Z
Indexed on
2012/10/24
17:13 UTC
Read the original article
Hit count: 315
I'm trying to make a decision for a new Windows desktop app: what to use for the UI. (This is a desktop app that needs to have compatibility with Windows 7. It won't be distributed on the Windows Store.)
This application is going to be cross-platform. I intend on writing the core in C++, and using each platform's native UI toolkit. I feel this is preferable to using a cross-platform toolkit like Qt, as it allows me to keep the native look and feel of each platform.
On the Windows side, the UI situation isn't exactly clear.
I'm getting the feeling that Microsoft is slowly abandoning .NET, particularly as their preferred toolkit for desktop apps. Indeed, the Getting Started chapter for Windows 7, as well as the rest of Microsoft's documentation, seems to be more suited for C++.
I have a few options here:
- C# with WPF - This sesms like this might be the best Microsoft has to offer for Windows 7 desktop apps, even if it isn't their "preferred" toolkit. I'd need to use P/Invoke to call my C++ code.
- C++ with Direct2D - This is what Microsoft used in one of their examples. This feels like it's too low-level. Part of the appeal of a higher-level UI toolkit is the consistency with the native look and feel of the platform, so doing this would just feel strange.
- C++ with a third-party UI toolkit, like Qt
There might be some other options I'm missing, which I'd love to hear about.
So, if you were starting a new Windows 7+ desktop app today, what would you use?
© Programmers or respective owner