3 ms·
Agreed. If iOS actually had a sane declarative language like Android's xml layouts then I'd do everything in code but since layouts coded in Obj-C are excruciat
by cageface 14y ago
Agreed. If iOS actually had a sane declarative language like Android's xml layouts then I'd do everything in code but since layouts coded in Obj-C are excruciatingly painful to read and edit you're better off with a WYSIWYG tool, even if (IMO) WYSIWYG is fundamentally the wrong approach for UI development.
I actually consider this a big liability for Apple going forward. The explosion of "phablets" and other form factors spells the end of their pixel-perfect design approach and their tools and APIs for managing dynamic, variable layouts are stone age compared to Android's.
- Zev 14y agoCocoa Auto Layouts are what you're looking for: https://developer.apple.com/library/mac/#documentation/UserExperience/Conceptual/AutolayoutPG/Articles/Introduction.html https://developer.apple.com/library/mac/#documentation/UserE...
- cageface 14y agoThey're better than nothing but compared to the html-esque layouts in Android they're much harder to write, read and debug.
- weiran 14y agoI would beg to differ. I much prefer to work with AutoLayout constraints rather than some custom XML layout like with Android or WP.
- cageface 14y agoYMMV but when the presenter of the WWDC AutoLayout track had to dig into Instruments to find out why his layout was throwing exceptions I felt like I was watching some kind of really nerdy April fools joke.