4 ms·
With my consulting work, I still end up doing a lot of desktop application development. I've been on the lookout for a GUI toolkit that I could use to replace W
by moron4hire 11y ago
With my consulting work, I still end up doing a lot of desktop application development. I've been on the lookout for a GUI toolkit that I could use to replace WinForms in my workflow. Ideally, it'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't check all those boxes, but I see no point in moving to WPF which checks even fewer.
So I get excited when GUI toolkit projects get posted on HN. And then I'm usually deflated when I look at the screenshots. I know they haven't built these programs themselves, so it'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.
https://www.wxwidgets.org/about/screenshots/ https://www.wxwidgets.org/about/screenshots/
Most of these examples feature something you should never do: selectively replacing the standard widgets from your operating system's toolkit. Either create/use a different toolkit entirely or use the defaults, don't mix and match.
It'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/CSS.
- mwcampbell 11y agoFWIW, I think Eclipse's SWT is the least bad option among cross-platform desktop GUI toolkits. Have you used it? wxWidgets is a close second, but there are some caveats. For example, for a native multi-column list view, you have to use wxListView on Windows, but wxDataView on OS X and GTK.
- jlarocco 11y agoI'm really not sure what you mean. wxWidgets is a wrapper around the underlying GUI framework. AFAICT, all of those screenshots are using the standard wxWidgets UI elements, with the obvious exceptions of the audio waveform, the on-screen keyboard, and the 3D graphics widget, which will not be standard components in any GUI toolkit. The variation is due to the users taking the screenshots using different themes or styles in Gtk, KDE, Windows, etc..
- moron4hire 11y agoI was not talking about those very purpose-specific widgets. I know they aren't standard components. I'm also not talking about theme- or OS-specific differences. I'm talking about the fact that few of the examples maintained a 100% consistent look and feel within their own theme. These are not nitpicky things. Maintaining visual consistency between applications is key to achieving usability. Here are some examples: All of the buttons are non-standard, but the gridview headers and tab controls are standard: https://www.wxwidgets.org/about/screenshots/cars-hotsurf-msw.png https://www.wxwidgets.org/about/screenshots/cars-hotsurf-msw... Non-standard toolbar buttons, repositioner handles, and rendering and location for tool-window close boxes: https://www.wxwidgets.org/about/screenshots/audacity-msw.png https://www.wxwidgets.org/about/screenshots/audacity-msw.png Skinned background and non-standard grouping panels, but standard buttons, menus, textboxes, etc: https://www.wxwidgets.org/about/screenshots/boinc.jpg https://www.wxwidgets.org/about/screenshots/boinc.jpg Non-standard coloring on buttons in toolbar: https://www.wxwidgets.org/about/screenshots/ginkgo-windows.jpg https://www.wxwidgets.org/about/screenshots/ginkgo-windows.j... Link-buttons used for commands ("Run Benchmark") and reskinned, giganto elements mixed with standard, tiny elements: https://www.wxwidgets.org/about/screenshots/sysmark2012.jpg https://www.wxwidgets.org/about/screenshots/sysmark2012.jpg An MDI hacked together out of grouping panels: https://www.wxwidgets.org/about/screenshots/trident-msw.jpg https://www.wxwidgets.org/about/screenshots/trident-msw.jpg There was absolutely no reason to reskin these buttons and textboxes. Skeuomorphism is bad design: https://www.wxwidgets.org/about/screenshots/audio-evolution-msw.png https://www.wxwidgets.org/about/screenshots/audio-evolution-... A hacked together Ribbon view out of a tab-view placed in the toolbar location, but they also include a separate toolbar section. Finally, that "calculate" button should follow its config elements, not precede them: https://www.wxwidgets.org/about/screenshots/coppercube-msw.jpg https://www.wxwidgets.org/about/screenshots/coppercube-msw.j...
- outworlder 11y agoYeah, these look pretty bad. If you are going to reskin, reskin everything. However, on Windows, you really cannot. Even more so if you are using the "classic" interface. On my last count, the scrollbars would redraw themselves in response to 11 different types of messages (not only WM_PAINT and WM_NCPAINT, as one would expect). And the API wouldn't give you a handle for you to draw them yourself, windows forms or not. Also, it doesn't help that most of the screenshots are quite old. Where are the apps running on Windows 10? The OSX screenshots, when present, are from the first OSX versions.
- witty_username 11y agoWhat do you think of Qt?
- maxxxxx 11y agoI am often in the same position. There are only more or less bad options, no good ones. Even on Windows only it's hard to pick a good toolkit for apps that can run from Windows 7 to App Store. I haven't used it much but Qt seems to the best option at the moment.
- moron4hire 11y agoI will have to look closer at Qt, then. The last time I looked at it, it seemed like it required a hefty licensing fee for commercial use and building forms required use of their janky editor. But that was a while ago, so it could have changed. The only proprietary editor I have room for in my life is Visual Studio, and even that is begrudging.
- kristianp 11y agoI'll agree that the featured apps are badly designed (overly reskinned), but I think they have been chosen because they are well known open source applications and also because of the rich set of controls used.