Well, to make life easier for those you seek help from: when you refer to third-party resources, be as specific as possible. For books, this means: title, author, edition, at least. Include chapter number and page number, if appropriate. "two books one by Robert Clair" is too vague for us to know what you're reading.Any advice to make life easier?
Both books cover Objective-C, so I'm not sure why they would already be talking about MVC in the first couple of chapters, since MVC is more of a Cocoa/CocoaTouch concept.I have gotten to chapter two on both books. I just find when they go into objects and Mvc it seems to go over my head. As they don't show exactly what is a model or view or controller and same goes for when they talk about methods etc
BNR = Big Nerd Ranch. I can't say anything other than I've heard the name of the book tossed around a lot here.Which book is BNR? Also you make some good points. I have decided to stick with Apples own language
http://www.macresearch.org/cocoa_for_scientists explains objects and methods nicelyI just find when they go into objects and Mvc it seems to go over my head. As they don't show exactly what is a model or view or controller and same goes for when they talk about methods etc
Sorry for the lack of information.
Now, I'll admit mvc is a weak point of mine, but I believe you're quite wrong on this.Small addition to the mvc:
The View and the controller tend to be located in the same file, the ViewController. The model is separate and is for example a NSObject. The model knows about your data and how to save it to persistence storage.