On Feb 15, 2011, at 8:50 AM, Marc Respass wrote:
> Keep in mind that in an NSDocument-based application, your NSDocument
> subclass *is* the model. You can have multiple windows all looking at the
> same model. You can get the document from the window's controller and the
> window from any vie
> I had not designed my program as a document-based application because I did
> not think that I would save and open data files. However, I have changed my
> viewpoint. It might also make implementing your suggestions easier.
>
Keep in mind that in an NSDocument-based application, your NSDocum
Thank you for the replies so far.
I had not designed my program as a document-based application because I did not
think that I would save and open data files. However, I have changed my
viewpoint. It might also make implementing your suggestions easier.
-Scott Steinman
__
On Sun, Feb 13, 2011 at 9:27 PM, Graham Cox wrote:
>> 3. When should the reference to the model be set up in each controller?
>
> It will be done for you when the document is created from the nib. All you
> need to do is populate the model from the file when the file is opened.
> NSDocument prov
On 13/02/2011, at 7:57 PM, Scott Steinman wrote:
> I'd like to split up the controller class into more manageable parts. I'm
> hoping to have one controller for the graphics NSView alone and another for
> everything else in the window. Both controllers would need access to the same
> model. W
Please forgive me since I'm a Cocoa newbie (having programmed in about a dozen
programming languages on many computer architectures -- this hints at my age!),
but I can't find an answer to what I think should be a simple question via the
Apple documentation, multiple Cocoa books, or web search e
