Re: Cocoa stripping resource forks: does Jaguar fix?
Re: Cocoa stripping resource forks: does Jaguar fix?
- Subject: Re: Cocoa stripping resource forks: does Jaguar fix?
- From: Sam Griffith <email@hidden>
- Date: Wed, 03 Jul 2002 17:56:19 -0500
On 7/3/02 5:10 PM, "Pierre-Olivier Latour" <email@hidden> wrote:
>
The day Windows will have the equivalent (if ever), it will become de-facto
>
a standard and I'm pretty sure, everyone will say: "how cool! Any app can
>
add custom tags to files without modifying the inner content!" ;)
Any OS X app can have the same thing as per my previous message. And Windows
apps use resources today too, so they can do some of this already. (They
stole it from the Mac. They even call them resources).
What is unique to the Mac files having resource forks is the way a jpeg file
can have that custom icon just for that one file.
With apps they've got a good way to get the same advantages, but on a single
file basis, the idea of having a resource fork is awesome. I just hope they
compleltely clean it all up and make the Cocoa libraries and Carbon
libraries work much better together.
Thanks for your reply.
--
Sam Griffith Jr.
email: email@hidden
Web site:
http://homepage.mac.com/staypufd/index.html
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.