First question, have you programmed anything in Cocoa? If so, you've probably climbed a few hills that seem incredibly easy now, but had you pulling your hair out trying to figure out what you were doing wrong.
You're going to have to define what level of experience you're teaching to. Are these completely green programmers? Do you have to teach what a variable is? Do you have to teach loops, conditional branching and basic C understanding before you delve into Objective-C and Cocoa?
I would look at a course like so:
1st - basic constructs, variables, loops, conditional branching (if, then, else, case statements, etc.).
2nd - Basic Objective C, message passing, OO design...
3rd - Memory management as in retain/release counts, some of the gotchas like what happens to retain count when you make a copy of a mutable object into an immutable object, etc. Memory management is key unless you like leaky apps.
4th - Interface Builder; show how to build a web browser with no code. Same thing with a rich text editor. Cover actions, outlets, delegates & First Responder. Cover subclassing and instantiating Objects. Cover custom views.
5th - Header files. This goes along with IB above. Teach how to understand header files, their usefulness, how they describe the object/methods of the object they are the header of. Show how to modify IB objects, then modify header files directly without using the Merge tool.
6th - MVC - Apple's Model, View, Controller hierarchy. Show how to split this up in Xcode. Explain why it's so important to segregate GUI control code from the rest of the app to simplify porting to other languages/OSs.
7th - Xcode & debugging tools. Most programs don't work right the first time so your students will need to learn how to debug their programs.
Other then the 1st point above, the rest will kind of mingle together and will probably need to be taught in a different order (i.e. cover MVC before delving into GUI apps).
The above could take you through 15 weeks of instruction.
Top
