I have 29 file types and wanted to get away from the if or switch to open them and let NSDocument pick the right class for me.
As I understand it, an Item in the Document types array of the plist contains and entry for an NSDocument class. And yes, each type has a unique extension (possibly multiple). I.e. type phobia has extensions pho, pho12, pho15 all mapped to NSDocument subclass MYPhobia. -koko On Jul 7, 2012, at 7:07 PM, Graham Cox wrote: > > On 08/07/2012, at 8:41 AM, koko wrote: > >> My Document Based Application is to have n document types. >> >> Is it then proper to create n subclasses of NSDocument and the corresponding >> plist Document types entries, i.e. Item 0 thru Item n-1 ? > > > > You can do it that way, or you can let a NSDocument subclass handle multiple > types if they are quite similar, or a bit of both. i.e. it depends. In my app > I have one document subclass for a number of filetypes, because they all end > up as the same document type with the same internal data model. > >> Is it true that all n document types will have a common extension but will >> be identified by the Document types entires? > > > If they all have the same extension then the system can't distinguish when a > file is opened by your app what document object class it should instantiate, > so that won't work. > > --Graham > > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
