Dealing with Resource Forks
Dealing with Resource Forks
- Subject: Dealing with Resource Forks
- From: Daniel DeCovnick <email@hidden>
- Date: Tue, 26 Oct 2004 01:53:57 -0400
Hello,
I'm trying to write a simple archiving program (testing an algorithm
mostly), but I've run into a problem: while the program works with most
Mac OS X files (read: files with data forks only), it doesn't work with
files with resource forks. While this isn't the terrible tragedy it
would be in the days of OS 9, there are still many files which depend,
in some cases entirely, on resource forks (EV Nova plugins, for
example), it only archives the data fork of the file and ignores the
resource fork entirely. When I un-archive the files, the data fork is
complete, but the resource fork is gone. Is there any easy way to deal
with the resource fork? Preferably something that doesn't require
knowledge of the internal structure of it? I know that Apple's ZIP
application splits the forks, and puts the resource fork in a __MACOSX
folder before archiving, but I'm not sure at all how that's done or
what the actual process is: does it split each resource into its own
file or does it keep them all in files based on each resource type, or
does it dump them all to a single resource file, and either way, how
does it do it?
Incidentally, I'd rather not use Carbon function calls if possible,
since I may end up porting this to GNUStep, at least for performance
testing.
Thanks,
Dan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden