Re: How to do what Finder does programmatically
Re: How to do what Finder does programmatically
- Subject: Re: How to do what Finder does programmatically
- From: Charles Srstka <email@hidden>
- Date: Thu, 24 Sep 2009 00:51:59 -0500
On Sep 24, 2009, at 12:29 AM, Ed Wynne wrote:
On Sep 24, 2009, at 1:25 AM, Jens Alfke wrote:
On Sep 23, 2009, at 9:38 PM, Gerriet M. Denkmann wrote:
If the document is a file, Finder will add a 'usro' resource which
contains the absolute path to the application to be used.
Thanks to Alistair who pointed me to: <http://sutes.co.uk/2009/09/creator-codes-are-not-replaced.html
>
So the ancient-but-elegant notion of a creator code has been thrown
out, to be replaced by the use of the ancient-but-lame resource
fork, as well as ancient-and-fragile hardcoded paths? :-P
A pity, sounds like the perfect use for an extended attribute.
Apple added this functionality before OS X had support for extended
attributes, so at the time the feature was implemented, there wasn't
really any way to do it other than the resource fork.
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