I am not totally sold on this new MVCS paradigm thats at the end of this chapter.
The model(BNRItem) class could have easily handled everything that the itemStore and the imageStore did(create items, connect to the documents directory and load images, etc). I suppose that if you wanted to create a generic imageStore class to hold all images in memory then that make more sense. Thats something that i can see being useful for any application that uses UIImage manipulation. I guess if i were writing this, createItem: and removeItem would have been one of my first methods to write for BNRItem. But then again, maybe I am all wrong here.
I, personally, have never had my controller save or load model objects. I thought the whole point of the MVC paradigm was that the controller would go to the model to get data and the model would get that data from a filesystem, database, or wherever and give that to the controller.
A store exposes a number of methods that allow a controller object to fetch and save model objects. The details of where these model objects come from or how they get there is left to the store.[/quote]
Again i thought that’s what the model in the MVC paradigm was supposed to be doing anyway??
Maybe i read this part wrong. maybe i am wrong. I am open to discussion because i want to continue to learn. Lets talk. :mrgreen: