3 ms·
I haven't done enough UIKit stuff to really comment on it, other than to say I also still find a lot of the conventions confusing or at least weird and also fin
by Strilanc 13y ago
I haven't done enough UIKit stuff to really comment on it, other than to say I also still find a lot of the conventions confusing or at least weird and also find that the documentation fails to answer my questions.
I also don't get the distinction between a UIView and a UIControllerView. In C# land I always associated view=.xaml and controller=.cs. In obj-c land both views and view controllers have a .xib and .m/.h, so it's not clear to me how responsibilities are divided.
- mmorey 13y agoA view can be a scene in a storyboard file, a xib file, or you can create your views programmatically (.m and .h). A view controller is always a .m and .h. And if you're not following the MVC pattern you can put your view code in your view controller's loadView/viewDidLoad method.
- Strilanc 13y agoThanks, that's actually a helpful thing to mention and obvious in hindsight. A view controller can be the owner of a .nib but not the class of a .nib, so the .nib is never a view controller. Are there particular divisions of responsibility that come up w.r.t. what you put in a view's .m/.h vs what you put in the controller's .m/.h? Is the .m/.h of a view considered to be a controller in the MVC sense but not in the UIViewController sense?
- tvon 13y agoA UIVieController has a view associated with it (typically self.view) which is why XCode offers to create a xib file for you.