as I can't think of any way to let a user specify the location
of a file without something that's equivalent to a path.
Well, if it were really needed, then he would have to build some
kind of
helper tool for it. Something that could produce an absolute path,
or a
relative path, or alias data XML'ified, and put it on the clipboard...
I thought of that, but his application sounds like a very atypical
application from the standpoint of Mac users if they can create XML
files manually that contain file references. Once you go outside the
norm that far I figure all bets are off. It also sounds as if
possibly alias behavior may actually be more robust than what he
wants, which is a valid perspective in some cases. My comments about
paths have be directed at more typical applications where things
should "just work" and the user should not be worried about them
breaking if he renames something, reorganizes his files or does
something as innocent as put some applications in a user-created
subfolder in the Applications folder or some such thing.
I'm not religiously opposed to paths. I simply think that as is
always the case, the file reference best suited for providing the
most desirable user experience should be used, and in most cases, for
persistent storage that isn't a path. It's even not the best at
runtime in some cases. Ever move a bundled application while it's
running? If you do, it won't be able to find anything in its own
bundle anymore.
Larry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
