Re: [Reposted] Document based resource strategy
Re: [Reposted] Document based resource strategy
- Subject: Re: [Reposted] Document based resource strategy
- From: Keary Suska <email@hidden>
- Date: Wed, 26 Nov 2008 09:37:01 -0700
On Nov 25, 2008, at 5:29 PM, Carlos Eduardo Mello wrote:
Guess I wasn't clear again... I'm not talking about the fact that
the NSDocument subclass owns the document window nib, as in
'iSpend'. What I mean is this: if you check the tableview in iSpend,
it has its datasource outlet connect to a TransactionsControler
object which was instantiated in the nib itself, while its delegate
outlet is wired to the File's Owner icon. Some document based
examples, instead of connecting its interface items to the FIle's
Owner icon, instantiate an object of the document subclass in the
nib and connect to it. My question is: how do the two types of
connection differ as far as the kinds of things you can do with them?
I am not sure what you mean to ask here. Do you mean whether the
NSDocument is a nib owner, as opposed to being instantiated in the
nib? I imagine it depends on what the author was trying to accomplish,
and since there are numerous ways a problem can be solved, there may
not be a specific reason why a certain approach was used (other than
it is what first came to mind). IMHO, NSDocument should not be
instantiated in a nib that contains the document-specific GUI. Again,
IMHO, I think NSDocument or it's NSWindowController should always own
the document GUI nib.
HTH,
Keary Suska
Esoteritech, Inc.
"Demystifying technology for your home or business"
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please 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