> Our product can be controlled by XML files. In certain cases, these
> XML files must contain a reference to further files. There are
> a certain number of customers who create their own XML files; they
> are not in general programmers, however. ...
>
> I cannot see our customers wanting to, or necessarily able to,
> generate alias records. ...
<http://developer.apple.com/qa/qa2004/qa1350.html>
Thanks for the reference. Unfortunately it simply suggests that an aliasref
be used, something that I feel is I'd already looked at and feel
is beyond some of those of our end users who generate the XML directly,
and are not explicitly programmers.
Also when we generate the XML which the user potentially modifies, using
less transparent representations will have an intimidating effect, I think.
The idea of contructing an FSRef piecemeal gives me another idea: since my
(cross platform) file access classes are an abstraction (on the Mac) on an
FSRef, I can simply take a POSIX path and, if it exceeds the maximum length,
break it up and make FSRefs the same way. The method for breaking up a POSIX
path being particularly well defined (separated on /, ignore repeated /)
this
seems robust. At this stage I see no particular benefit to asking the user
to contruct a URL.
Thanks to all,
Aandi Inston
_______________________________________________
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
This email sent to email@hidden
