13 ms·
My favorite cross-platform GUI toolkit ever was/is Cocotron: http://cocotron.org http://cocotron.org Let's face it, macOS is the only desktop platform where u
by pavlov 10y ago
My favorite cross-platform GUI toolkit ever was/is Cocotron:
http://cocotron.org http://cocotron.org
Let's face it, macOS is the only desktop platform where users give a shit about whether apps look native and use system-provided controls. Mac is also the platform that has the nicest standard UI framework (Linux doesn't have one and Windows is forever haunted by Win32 despite Microsoft's 15 years of trying to push XAML).
Hence it makes sense to build desktop GUIs for Mac first, on the Mac, and cross-compile to other targets. Cocotron delivered just that: a minimalist BSD implementation of Foundation + AppKit, with a footprint light enough that you won't be ashamed to ship it as a DLL with your Windows app.
I've used Cocotron a couple of years ago for some custom graphics apps that needed to be deployed on Windows (one was a title creation app for a TV game show, just to design the graphics they needed for each weekly episode). It worked great. Even accounting for Cocotron's missing pieces and bugs, the UX of Cocoa-on-Windows was lightyears better than what people were used to when it comes to custom Windows apps.
Unfortunately Apple hasn't really made life easy for Cocotron because the platform has moved ahead so fast and Objective-C has accumulated tons of slightly warty features for Swift bridging.
The original OpenStep/Cocoa was clean, small and designed to be portable with light compiler support. Today, Apple APIs are a sprawling foundation for the iOS ecosystem, and it's in Apple's interest to keep making the API surface bigger and harder to port so that nobody can pull off what Microsoft tried with their iOS bridge [1]. (Obviously I don't blame Apple in any way, just feeling slightly nostalgic.)
[1] https://developer.microsoft.com/en-us/windows/bridges/ios https://developer.microsoft.com/en-us/windows/bridges/ios
- fake-name 10y ago> Let's face it, macOS is the only desktop platform where users give a shit about whether apps look native and use system-provided controls. Citation VERY MUCH needed. I'm on windows, and I care about applications using native widgets. I mostly care because non-native widgets tend to have horrible performance, but windows does have at least some consistent styles (there are several, but there is some consistency), and a lot of custom windowing libraries just look horrible, and more importantly, behave inconsistently. I'll generally be willing to use odd-looking GUIs, but when you have an odd-looking GUI that has different behaviour then is standard, it really annoys the hell out of me.
- mikewhy 10y agoThe right-click menu is a different style between the desktop and the title bar. Right out the gate there are so many inconsistencies in Windows I can really see where the person you're replying to is coming from.
- iaml 10y agoCase in point, if you want to change some setting in w10 you may want to look in one of the following locations: Control panel (1), Control panel (2), Registry, Group Policy Editor, some random menu or other program you need to launch. Really screams "consistency" doesn't it?
- ta34534445 10y agoI agree with your example completely. However this doesn't mean users don't appreciate native widgets and UI consistency. In fact, this is a common complaint for windows, something that Microsoft is currently working on (at what ever pace) Microsoft is firmly in the backwards compatibility at all costs camp - something which I definitely appreciate. This however comes at a cost and your example is one of them. I'm not suggesting this is not avoidable, but the complexity should not be understated.