FROM : Matt Gemmell
DATE : Wed Jan 29 20:23:50 2003
On Wednesday, January 29, 2003, at 05:58 pm, James Pengra wrote:
> In a document-style application I want to open a window in which to
> make an analytical plot of some data. This window will always be
> associated with with a main document window. I only want the window
> visible when called by the user.
> I could create a window with its own Nib file and Controller, but I
> discovered the concept of a Child Window, and wonder if that would be
> a better approach. I don't find a lot of discussion or use of Child
> windows in the books I have, or even in Apple's documentation.
Not entirely sure what you mean by a child window, but If you're
opening a secondary view or alternate representation of the same
document's data/content, you'd probably do so by associating an
additional WindowController (and its window) with the same
DocumentController. I'm sure Aaron's and Scott's (et al) books discuss
the hierarchy of doc-controllers to window controllers to windows.
You'd just have two window controllers, each with its own window, owned
by the same doc controller.
Best,
-Matt
--
Matt Gemmell
Scotland Software
http://www.scotlandsoftware.com/
_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
DATE : Wed Jan 29 20:23:50 2003
On Wednesday, January 29, 2003, at 05:58 pm, James Pengra wrote:
> In a document-style application I want to open a window in which to
> make an analytical plot of some data. This window will always be
> associated with with a main document window. I only want the window
> visible when called by the user.
> I could create a window with its own Nib file and Controller, but I
> discovered the concept of a Child Window, and wonder if that would be
> a better approach. I don't find a lot of discussion or use of Child
> windows in the books I have, or even in Apple's documentation.
Not entirely sure what you mean by a child window, but If you're
opening a secondary view or alternate representation of the same
document's data/content, you'd probably do so by associating an
additional WindowController (and its window) with the same
DocumentController. I'm sure Aaron's and Scott's (et al) books discuss
the hierarchy of doc-controllers to window controllers to windows.
You'd just have two window controllers, each with its own window, owned
by the same doc controller.
Best,
-Matt
--
Matt Gemmell
Scotland Software
http://www.scotlandsoftware.com/
_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
| Related mails | Author | Date |
|---|---|---|
| James Pengra | Jan 29, 18:58 | |
| Matt Gemmell | Jan 29, 20:23 | |
| Ryan Stevens | Jan 30, 04:44 | |
| Ian G. Gillespie | Jan 30, 17:49 | |
| Bill Cheeseman | Jan 30, 22:40 | |
| matt neuburg | Feb 3, 01:50 |






Cocoa mail archive

