Model View

Question

Would it be natural to have the Views in the Designer interface bind to variables and actions in a single location, so that all data, including available actions, data, instance variables, and P-list variables, etc are in one location and one Interface?
I just noticed how smooth development would be for me if, after setting out the CoreData Model, I could bind the view in the design Interface to the fields in the Core Data Model, and then pull the values in those field into and out of Classes. It would make the entire Cocoa schema more clear to my beginner's mind, especially if a Data Model design interface appeared to have several different sections for Core Data entities, available classes and methods, P-list variables, instance variables, etc. I'm even wondering if it's worth setting up some kind of unified data/variable interface before I go farther into developing?

Answer 1

While it may seem like my posts are not following any logical development, it is not so.
My previous posts have been learning about the systems for data output from the application.
This post is the contrary, or flip-side. Not how data is input into the application, but the possible systems for inputting data into the formulation of the application itself.
It looks like P-lists are a mini form of CoreData, and also protocols a means to create a central data location for declared properties. So there are three places in use through which data can be extracted and replaced by class instances.
What I'm saying is, if the the three locations were linked into one interface, and the view interface could link directly to the data at those locations, then the classes would simply pull, change and replace data as required by their code and all of Cocoa would be much easier to use and understand?