On Sep 17, 2014, at 19:18 , Charles Jenkins <cejw...@gmail.com> wrote:
> What configuration am I missing to get a document package which appears as a > single file? You edit this directly in Xcode, though you’re correct that the documentation doesn’t really pull all the pieces together to give you a clear idea of what to do. Select the project item at the top of your navigator, then select the appropriate target, then select the Info tab. — If you’re creating a document of a new type, then you should create a new entry describing the type in the “Exported UTIs” section. — If you’re creating a document of a type defined by something else, but not a standard type, then you should create a new entry describing the type in the “Imported UTIs” section instead. (In this case, the purpose of describing it is to provide the details in case the owning application isn’t installed in the user’s Mac.) — Then, create a document type entry that references the UTI you already defined. (Note that there are some duplicate fields, such as file extensions, which are holdovers from the days when there weren’t UTIs. The UTI information should prevail.) For a package, there are a couple of things you must do. From memory: — Make sure your UTI conforms to “com.apple.package" (kUTTypePackage). I think it should also conform to “public.data”, but it would be safer to check the NSDocument programming guide yourself, where this is spelled out (somewhere). — Check the box in the file-type entry that says it’s a package. _______________________________________________ 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
