3 ms·
> On macOS and iOS, it’s not just built into every app, it’s built into the operating system itself. It’s a fundamental feature of Cocoa, open which all native
by PaulDavisThe1st 6y ago
> On macOS and iOS, it’s not just built into every app, it’s built into the operating system itself. It’s a fundamental feature of Cocoa, open which all native apps are built, so every app gets the correct behaviour for free. Dragging and dropping is super powered on Apple platforms.
This isn't true. It is true that it's built into the development tools and toolkits that Apple provide and expect you to use when writing software for their platform.
But it's not particularly hard to avoid. Google "nibless development mac" and you'll find some links that reveal how to develop full GUI apps on macOS that do not rely on this infrastructure. Regardless of whether or not you think this is a good idea, please rest assured that an application developed in this way does not share the "OS-level" drag behavior that you describe above. For it to behave in this way requires explicit code to handle notifications delivered by the OS.
Why does this matter? Because those Apple SDKs that make all this happen "seamlessly" are hard to use if you want to do cross-platform development. Qt (and GTK) work at trying to take care of this for you, but its not 100%, precisely because (as you note) this concept doesn't exist on other platforms.
So yes, from a user perspective this is a "universal" feature of apps on macOS. But it does not come with the OS - it comes from only developing apps using Apple SDKs and tools, which makes it harder for people doing cross-platform development to correctly play the game in the expected way.
- zapzupnz 6y agoMy only response to that is apps that aren’t made to be good macOS citizens wouldn’t even vaguely register on my radar as ‘native’, even if they link against Cocoa. ‘Native’ on Apple platforms isn’t just a technical description, it’s also about UI and, more importantly, UX. Of course, Apple are starting to muddy the waters with UIKit for Mac — but even then, the fact that iOS apps can now run ‘natively’ on macOS goes a long way to showing that just because an app links against the relevant frameworks compiled for the right processor architecture, that doesn’t make it native in the Apple-y sense. Apps made using cross-platform frameworks like Qt and GTK certainly don’t register to me as native. They don’t just work differently, they even look odd. I don’t think this fazes Windows and Linux users/developers as much because there has never been any level of consistency remotely close to what Cocoa and macOS offers — if an app puts a few buttons in a slightly odd place, that’s not seen an a problem. So I agree with your point on a technical basis that my assessment wasn’t 100% technically true — but I think from the point of view of what ‘native apps’ means when discussing Apple platforms, I don’t think I’m too far off the mark.
- PaulDavisThe1st 6y ago> My only response to that is apps that aren’t made to be good macOS citizens wouldn’t even vaguely register on my radar as ‘native’, even if they link against Cocoa. Sure. But two things: 1) I wasn't saying that an app that use nib-less techniques couldn't do the right thing - it could. It could appear totally native if someone just does the work. 2) There are several pro creativity apps (Logic, Mainstage being the biggest) that are actually Apple products but they do not adhere to Apple guidelines. They use non-standard widgets, do not fully follow desktop interactivity guidelines, use the keyboard in non-standard ways. So even within the set of Apple's own applications, there are things that are about as different as a Qt or GTK application might be.
- zapzupnz 6y agoI agree on those points. Especially on the first: when people put in the hard work, those pay dividends — but often mean those apps lag behind when Apple does breaking changes (which must happen at least every 3 or 4 years). Apple’s Pro-apps are very alien. I expect that’s because they appeal to an audience that spends almost all their time in them, not moving much between a whole bunch of apps. Lastly: Nothing’s ever as non-native as a GTK app. :D Qt and Wx apps do an infinitely better job than any GTK app I’ve seen for macOS, even if I don’t think they come very close aside from tapping into Cocoa’s control drawing.