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: Isaac Sherman <email@hidden>
- Date: Wed, 03 Jul 2002 15:46:42 -0400
So, I take it the upshot of this thread is that there's no chance of me
porting ResEdit to Cocoa? Another project bites the dust...
From a simplified, newbie's point of view, I'd say, "There apparently is a
problem involving data-loss when using Cocoa. Cocoa is intended to be used
on Macs, which are in turn expected to be capable of handling files for the
Classic environment, the capability should be there. It needs to be fixed."
I fail to see the argument: would someone please explain it to me? I must
have missed it somewhere.
Someone in this thread said, "Think different- Think compatible"; the idea
is just to extend Cocoa's compatibility, is it not?
And I think it's great that we have a Jedi on our side. ;-)
Thanks,
--
Isaac Sherman
MotaSoft Software
http://homepage.mac.com/huperzoevs/
_______________________________________________
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.