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: Sun, 07 Jul 2002 03:22:49 -0700
Well, I don't want to belabor this any more, and I agree with you that a
well-behaved app should deal with as many contingencies as possible.
But I did want to raise exception on two points, because they're kind of
key to making this transitory period work.
Michael Tsai wrote:
Personally, I think the Finder's too slow at this, for large images
and/or images on slow volumes. Having a cached preview is often nice.
It's also the only way to have a preview for formats the Finder
doesn't understand, e.g. FrameMaker.
Not true. The Finder can be extended (via some kind of plugin, i
believe) to preview any kind of file by examining its contents.
Yes, you could store the custom icons elsewhere. Yes, that might have
efficiency advantages in certain cases. But then every utility that
wanted to copy a file would have to know to copy the appropriate part
of the invisible Icon file.
No, that would be handled by EXACTLY the same API that handle it now.
Those API would simply have to be modified to look in the right location.
Thanks to all for some great discussion on this topic. It could have
easily degenerated into flamewar.
--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.