I can write factory methods to create control types with application-specific styling already applied.Personally, I find some of the benefits of code-only to be: I happen to be in the opposite boat - I've found them to fragment my code and hinder efficient development. If you need to globally reconfigure something, consider procedurally generating part or all of that part of the UI.Īnd for your own sake, use SEVERAL storyboards for the different parts of the app, Not one jumbo board with 100 view controllers specced out in it.
If a storyboard way to do something isn't working, whip out the code and programmatically make that feature. That said, the people who use them most successfully do not do absolutely everything in the storyboard, they definitely mix some code in there to make it all go easily. If you choose to avoid them, that's totally an option for you, but if you want a job doing iOS work, eventually, you will probably need to come to terms with IB. Storyboards are pretty good at a few things, quite bad at a few other things.
Some older apps do not (as they started with NIBs) I've been doing iOS development full time for 7 years
0 kommentar(er)
