Last year I posted an article that talks about why I stopped using Interface Builder in favor of writing code to create views. There are some who disagree with me, and to them I say, “To each his own.” And there are some who agree with me, but choose not to publicize it. No matter. Every programmer has tricks that make them more productive, and creating views in code just happens to be one trick that works well for me.
What works for me doesn’t necessarily work for others. But I have to say, I had a brief “HA!” moment when I read this comment from Peter Steinberger’s post about researching Apple’s research kit:
All views are created in code. Apple uses a Storyboard for the example catalog, but that’s it. Apple uses the standard pattern of overriding
viewDidLoadto build UI in combination with Auto Layout and the visual format language, whenever possible.
Great minds think alike.1
-
Though I don’t override
viewDidLoadto create my views. I usually create a view class, and I add an instance of the class to the view controller’s view inloadView. ↩
Posted in programming. Tagged in ios.
Related Articles
- Advice for new iOS freelancers
- How I post to my Jekyll site using my iPhone
- The Experienced Programmer's Guide to Getting Started with Swift
- From Trace To Slopes
- How To Do A Case Insensitive Search Using Parse SDK
- How To Present An Alert View Using UIAlertController When You Don't Have A View Controller
- My Upcoming Share Extension Talk At 360idev-Min
- Wish I Could Help But It's Not My App
- Maintain Your iOS App With Peak App Care
- Boston Area Mac And iOS Dev Community Is Awesome