Re: opening file without an extension
Re: opening file without an extension
- Subject: Re: opening file without an extension
- From: Charles Srstka <email@hidden>
- Date: Wed, 04 Jul 2012 15:15:03 -0500
On Jul 4, 2012, at 3:03 PM, Kyle Sluder wrote:
> On Jul 4, 2012, at 12:54 PM, Charles Srstka wrote:
>
>> On Jul 4, 2012, at 2:40 PM, Sean McBride wrote:
>>
>>> On Sun, 1 Jul 2012 20:21:39 -0700, Todd Heberlein said:
>>>
>>>>> Does putting an asterisk (*) in the Extensions field for your document
>>>> type not work in the sandbox?
>>>>
>>>> Excellent! Yes it did.
>>>
>>> Umm, why not just use the documented technique?
>>
>> Because that’s exactly what this is?
>>
>> http://developer.apple.com/library/mac/#documentation/general/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html#//apple_ref/doc/uid/20001431-101705
>
> As the documentation states, you should not be using the Extensions field (which maps to CFBundleTypeExtensions), as they have been deprecated in Mac OS X 10.5. Use UTIs instead.
For the general case, you want to use UTIs instead of extensions; however, this is a special case, and there’s not really an equivalent way to do this with UTIs. In theory, registering for public.data should work, but at least when I tried this about a year ago, it caused the Finder to do some really strange things. I can’t really remember the details anymore, but I do remember that the beta testers were screaming. If you look at Xcode’s Info.plist to see how they registered as a handler for all files, you will see that they put * for CFBundleTypeExtensions; that’s a good enough sign to me that that’s how we should do it, for now at least.
Charles
_______________________________________________
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