3 ms·

I tried to understand NIB mechanism and it was opaque. I like having everything represented in code, rather than spread across two different tools. This NIB-t

by rayval 16y ago

I tried to understand NIB mechanism and it was opaque. I like having everything represented in code, rather than spread across two different tools. This NIB-to-code utility seems worthwhile.

shaggyfrog 16y ago
I used to think "everything should be in code" as well, when I started iOS development. But after I used IB for a while, I could see how it was saving me time on certain tasks, like setting up the ol' MainWindow.xib (especially if you have nested view controllers). That said, it's not as good working with complex, custom views. There, I go all-code. I think this is the pragmatic approach.