What, exactly, makes a Cocoa project document-based?
What, exactly, makes a Cocoa project document-based?
- Subject: What, exactly, makes a Cocoa project document-based?
- From: Rick Hoge <email@hidden>
- Date: Sat, 18 Jun 2005 00:22:44 -0400
I've done a lot of stuff with Cocoa doc-based apps, but recently had
kind of an existential question:
When you select 'Cocoa document-based application' as a new project
type, what are all the specific elements added to make it this kind
of app?
The following are obvious:
- files implementing an NSDocument subclass are created
- a document nib is created whose owner is the NSDocument subclass
- the info.plist file has document-related information
So what else is done specifically for a document-based app? Where
does the NSDocumentController come from?
Thanks very much for any comments on this - I am considering
modifying some programs which are currently based on the standard
multi-document/multi-window template to use a single-window
organizational view for multiple documents and this question came to
mind.
Rick
_______________________________________________
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