• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Cocoa stripping resource forks: does Jaguar fix?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cocoa stripping resource forks: does Jaguar fix?


  • Subject: Re: Cocoa stripping resource forks: does Jaguar fix?
  • From: John Haager <email@hidden>
  • Date: Wed, 3 Jul 2002 18:47:43 -0700

On Wednesday, July 3, 2002, at 02:13 PM, Pierre-Olivier Latour wrote:

There is (presumed some, I guess, 10% of code would be Carbon, which
is no problem for Cocoa links agains Carbon anyway), but what on
earth for?!? Those OS9 resources are OBSOLETE!!! Any new application
should use resource data stored in separate files inside a bundle
instead.

FYI: resource fork is the best way to add "special data" to files like
preview pictures (very useful, unless you're a real UNIX terminal only geek
;) ), print settings, custom icons, and lot of other stuff. Furthermore, all
this non-essential information is added _without_ touching the original data
which remains usable on other file systems.

And for ancillary, non-essential data such as preview images, it's fine. If I lose the resource fork, nothing critically important is lost. However, I do take issues with apps (such as Quicken 2002) which store over half their data in the resource fork.

Found this out the hard way when I used 'cp' to move my home dir from one laptop to another. Quicken refused to even open its data files without the resource forks. When I did finally, after much wailing and gnashing of teeth, get it to open it, I found out that it stores my preferences, my scheduled transactions, my memorized transactions, and all sorts of other info in there. The only things that were still intact were the actual registers themselves.

So, resource forks are fine if you want to use them for ancillary data. But your program should still open the files if that data has been stripped off.

And on that note, I'm gonna leave my two cents and go.

-> John Haager <-
_______________________________________________
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.

References: 
 >Re: Cocoa stripping resource forks: does Jaguar fix? (From: Pierre-Olivier Latour <email@hidden>)

  • Prev by Date: how would you allow editing of a combo box's values?
  • Next by Date: Fun with MallocDebug
  • Previous by thread: Re: Cocoa stripping resource forks: does Jaguar fix?
  • Next by thread: Re: Cocoa stripping resource forks: does Jaguar fix?
  • Index(es):
    • Date
    • Thread