Re: Aliases & fileAttributesAtPath:
Re: Aliases & fileAttributesAtPath:
- Subject: Re: Aliases & fileAttributesAtPath:
- From: email@hidden
- Date: Sun, 14 Oct 2001 22:20:48 +0930
If you look at the defaults read output for com.apple.dock you see the
key "file-data" equal to a dictionary with three keys, _CFURLAliasData,
_CFURLString, _CFURLStringType. I read somewhere in the carbon doc's
that you should be moving to using CFURL's, perhaps apple will wrap up
the alias mechanisms within CFURL's and NSURL's, since their
implementation is hidden. I'm using NSURL's for storage within the app
I'm currently working on but my brief tests seem to suggest that there
is no alias mechanism going on yet.
On Sunday, October 14, 2001, at 08:49 PM, Ondra Cada wrote:
CH> >They would, on the other hand, break almost anything what used to
work
CH> >originally, from shell scripts through posix or BSD API tools to
Cocoa
CH> >applications.
CH> >
CH> >Soft and hard links though work quite properly with all that.
CH>
CH> Cocoa doesn't default to resolving aliases in the middle of paths?
CH> That's bogus. Just points to more need to update Cocoa to handle
CH> FSRefs and AliasRecords. Of course, you should never actually be
CH> *storing* paths as persistent file references, so neither you nor
CH> your users should actually encounter such a situation in common use.
This is exactly the Mac OS 9- speak I am so angry with.
The file path is, always was, and always will be the primary means to
reference a file: it is intuitive, easy to use for both programmer and
user,
and, which is the important thing: