Re: Cocoa newbie app architecture / dialog question
Re: Cocoa newbie app architecture / dialog question
- Subject: Re: Cocoa newbie app architecture / dialog question
- From: Keary Suska <email@hidden>
- Date: Fri, 15 Dec 2006 11:57:29 -0700
- Thread-topic: Cocoa newbie app architecture / dialog question
on 12/14/06 9:10 PM, email@hidden purportedly said:
> I have a basic question about correct relationships in my code. I have an
> application that supports multiple documents (one window per document). Each
> document can potentially open its own copy of a modal dialog ("panel"), that
> operates on the contents of that document. I'm trying to understand who ought
> properly create the (custom) window controller associated with the dialog.
There is not enough info provided to offer a decent solution, but there are
some common approaches. If the functionality of this "panel" is analogous to
a preference panel or a font panel, the common approach is to use a window
controller and a separate nib. In a straightforward implementation, the
controller is instantiated by the app delegate. If you are using the shared
document controller (i.e. not creating your own instance or subclassing),
getting access to the current document is fairly straightforward.
Otherwise, we would need more info on what the panel does and how it works
in order to offer possible solutions.
Best,
Keary Suska
Esoteritech, Inc.
"Demystifying technology for your home or business"
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden