the xcode follies part two: fail
OK. So maybe a title such as ‘fail’ is a bit on the pessimistic side and doesn’t accurate describe the truth of my current situation.
Here’s what I’m toiling over now: Frameworks are not libraries, global variables are unnecessary and methods pass messages rather than variables and values. You could write the Controller and Model code into the same class, but this would be unconventional. Cocoa is merely a term that is used to described a framework that is simply a conglomerate of several other frameworks that make up the core developmental set for OS X (but do NOT confuse this with a library).
In all seriousness, I’m really starting to understand the Model/View/Controller (MVC) design pattern. It is very similar to the integration of CSS into the web with the seperation of content (Model) and presentation (View). Integrating client-side or server-side logic to automate the interaction between content and presentation thus becomes your Controller.
So most of this is coming together. The only problem is I can see each individual piece quite clearly, however, when looking at the whole from a greater distance, the edges get fuzzy. I have a feeling I’m one or two blanks away from filling them all in and THAT is the exciting moment in such an endeavor. Can’t wait to put the pieces together and roll it all up into a tangible and meaningful knowledgebase to build and grow on.
More to come.