WxWidgets 3.1.0 Brings Better HiDPI Support, WxQt with Qt5
With my consulting work, I still end up doing a lot of desktop application development. I&#x27;ve been on the lookout for a GUI toolkit that I could use to replace WinForms in my workflow. Ideally, it&#x27;d be cross-platform, support native widgets, and provide the de facto standard OO API that every other GUI toolkit has converged on. I know WinForms doesn&#x27;t check all those boxes, but I see no point in moving to WPF which checks even fewer.<p>So I get excited when GUI toolkit projects get posted on HN. And then I&#x27;m usually deflated when I look at the screenshots. I know they haven&#x27;t built these programs themselves, so it&#x27;s not necessarily their fault that these developers have gone with the everything-and-the-kitchen-sink style of UI design. But they also chose to feature these particular projects, so someone there thinks these are good examples, which does not speak well towards their commitment to enabling good design. 
<a href="https:&#x2F;&#x2F;www.wxwidgets.org&#x2F;about&#x2F;screenshots&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.wxwidgets.org&#x2F;about&#x2F;screenshots&#x2F;</a><p>Most of these examples feature something you should never do: selectively replacing the standard widgets from your operating system&#x27;s toolkit. Either create&#x2F;use a different toolkit entirely or use the defaults, don&#x27;t mix and match.<p>It&#x27;s disheartening to think that, in 2016, the least-bad way to design a UI is to wrap up a browser as a widget and sling HTML&#x2F;CSS.