Re: Document Architecture question - newbie
Re: Document Architecture question - newbie
- Subject: Re: Document Architecture question - newbie
- From: Doug <email@hidden>
- Date: Fri, 28 Oct 2005 13:00:03 -0700 (PDT)
Bill Bumgarner wrote:
> The only other trick to all of this is where to put
>the various controllers (ArrayController,
>ObjectController, and TreeController) such that the
>various document windows will correctly track
>selection, etc. If you have a "main" window, then
>stick 'em in there. The "auxillary" windows can
then >have bindings through paths that lead to the
"main" >window through the file's owner. This
paragraph >will make no sense until you have a solid
>understanding of NSDocument's interaction with the
>window controller, controllers, and keypaths.
>
> b.bum
>
Thanks a lot for the response,
I do need to rephrase part of the question:
I would like to subclass NSDocument for my "main"
document (and main window). That window will display
data from a variety of files. I want to keep them
independent so that file "x" could view data file a,
b, c and file "y" could view data file b, c, d, and e
or whatever.
My question is, can I leverage the functionality of
NSDocument for the data files as well? My suspicion
is that it could work if the controllers were set up
correctly. If so where should the code for contol of
the data files logically fit in the MVC structure?
Thanks again,
Doug
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden