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: Matt Judy <email@hidden>
- Date: Sat, 06 Jul 2002 17:45:44 -0700
I'd just like to respond to a few points I've read:
It seems to be generally accepted that bundles do a good job for
packaging up the "resources" that formerly resided in an app's resource
fork. And it seems that the main reasons people want resource forks for
single files are file previews and custom icons.
Now, it seems to me that Mac OS X (read: Finder) does a pretty good job
of generating its own preview, on the fly, for any file of a
QuickTime-supported format. Also for text, RTF, and PDF. So the better
approach is being taken here: actually reading the file for its preview.
No resource forks needed.
As for custom icons, Mac OS 9 has LONG used separate, invisible Icon
files to store icons when a resource fork wasn't an option. There's no
reason that all custom icons couldn't be stored in such a file. Over
slower network connections, custom icons are what slow down file
listings. By putting them in one auxiliary file, and loading
progressively, you would actually increase transfer and display efficiency.
And getting back to the original example... the .webloc thing... When
you drag a bookmark out of IE, it creates a .url file. That file only
opens in IE, every time, regardless of your preferred browser. If you
want to create a .webloc file, which opens in your specified browser,
you'll have to drag the link out of a different browser (Mozilla/OmniWeb).
-- Matt
_______________________________________________
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.