Re: Write a prefs file
Re: Write a prefs file
- Subject: Re: Write a prefs file
- From: JollyRoger <email@hidden>
- Date: Wed, 29 May 2002 20:35:12 -0500
On 5/29/2002 8:01 PM, "Ric Phillips" <email@hidden> wrote:
>
On 29/5/02 6:20 AM, "Emmanuel" <email@hidden> wrote:
>
>
> At 4:42 PM +0200 28/5/02, Paul Berkowitz wrote:
>
>
>
>> The Satimage osax, which you can now get separately from the script editor
>
>> Smile, also writes resources. In addition, Satimage exists in an OS X
>
>> version.
>
>
>
Although resource forks are a part of the HFS+ architecture, I thought the
>
recommendation was that resource forks are out, and should not be used any
>
more. Preference data should go into a plain text config file (data fork)
>
and in XML syntax to boot. Existing files can be examined (and new files
>
created) with the property list editor that comes with the development tools
>
CD or download. Under AS studio, even the binary stuff, dialog boxes, icons,
>
etc are going into the data forks.
Consider the source.
HFS+ supports data forks just fine, even on Mac OS X. The only valid reason
for not using resource forks is if you plan on placing the file on a
non-HFS+ volume, such a UFS or NTFS. And since AppleScript doesn't run on
Windows, that rules NTFS out for this case. UFS is a horrid file system
that the Unix-folk at Apple are desperately trying to push because it's what
they are used to, even though HFS+ is light-years ahead of UFS in almost
every respect. As long as Apple supports HFS+, resource forks are fine and
dandy - and rest assured Apple isn't moving away from (not to mention
removing support for!) HFS+ any time soon. Apple itself continues to use
resource forks in LOTS of Mac OS X software. What's good enough for
Apple.....
JR
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.