Quote:
Originally Posted by dicklacara
So, on the iPhone (or the server, for that matter), a View or VC that wants to access the "array" does so by referencing the appDelegate. In effect, isn't the appDelegate acting as the "model" even though it has subordinated the creation, maintenance and manipulation of the "array" to other classes?
|
No, view controllers get a *reference* to an array controller from the app delegate. Once the reference is obtained, they use the array controller directly. The array controller is a proxy to the actual array.
Quote:
|
What happens if a VC wants to search or sort the array for presentation does it do that itself, or request it from the "model" controller through the appDelegate?
|
Well, sorting is tricky when not all of the objects have yet been downloaded or if they've been removed from RAM temporarily due to memory constraints. So I leave that up to the controller. (not the vc)
Quote:
|
I would gladly help in any way I can. I am relatively new to Cocoa, but I understand the concept and see the need to define "where to put the data and the methods to manipulate it".
|
That's cool. I wrote down some ideas on how to generalize this. It might start as a tutorial and then grow into something that could be reused.
