4 ms·
The home app currently shipping with Mojave did this[1] much to everybody's amusement. Of all the iOS controls, this is the one that handles the worst on the m
by pilif 7y ago
The home app currently shipping with Mojave did this[1] much to everybody's amusement.
Of all the iOS controls, this is the one that handles the worst on the mac.
[1]: https://i.imgur.com/B8TWtTg.png https://i.imgur.com/B8TWtTg.png
- saagarjha 7y agoThe Home app is using UIPickerView on Mac when it should really be using NSPopUpButton. Likewise, Mac apps using NSPopUpButton should use UIPickerView on iOS. At least, that's my view of things.
- pilif 7y agoyes. Or even better, there should be a new abstract control with a semantic "chose one in a list" meaning that renders as an UIPickerView on iOS and an NSPopUpButton on the mac.
- bobbylarrybobby 7y agoThe issue is that times are more easily typed out on a Mac, but a scrolling picker makes sense on an iPhone
- grey-area 7y agoThe whole point of any merge is that one entire UI framework goes away. There is no way Apple will keep two entire APIs available after a transition period. It looks to me like iOS will win, this has been obvious for some time based on the revenue and new API work: https://news.ycombinator.com/item?id=4776859#4777354 https://news.ycombinator.com/item?id=4776859#4777354
- saagarjha 7y agoiOS may "win" in the sense that UIKit on the Mac gets the blessing of being the preferred way to develop apps, but I would eat my hat if Apple decided that UIPickerView's stupid spinny wheel was the "new" way of doing list selection on macOS. I think it is significantly more likely that UIPickerView ends up being "themed" on macOS to look like NSPopUpButton.
- grey-area 7y agoSure, they'll present some controls differently, and some controls for Mac OS will need to be added (for menus for example). I'd expect them to attempt to keep differences in presentation to a minimum though.
- JeremyBanks 7y agoPrepare to eat your hat: Tim Cook's Apple doesn't give a fuck about MacOS.