Thank you Robert for commenting on my alert alert and for
giving us additional insights!

You are perfectly right with your remarks but I'm not wrong either.

Indeed:

> ...Apple wishes to get rid of resources as soon as possible

even if this may appear "frightening" to some of us.
Ok, I should have better stated "old style" resources.
(foreseeable future ?=? as soon as possible)

Actually, there is much more behind the scenes.
With resources in the data-fork we shall see new tools (bye,
bye ResEdit, etc.), (additional) toolbox calls and ways of
handling (new) resource data!
Our programming practice must change. See e.g. your #4 !
IMHO, being informed about changes leads to code that lives
longer than that created according to outdated -- but
presently tolerated -- coding habits. :-)

Happy coding and best to you all,

Herbie

**************************************
Robert wrote:

This overstates the case. The story, as I understand it, is:

1. Resources will continue to be supported for the
foreseeable future.
2. The resource FORK is currently supported in OS X, but may
be phased 
out. Instead we will be increasingly encouraged to create
'bundled' 
applications whose resources are contained in the DATA fork
of a 
separate resource file.
3. Resource Manager routines (GetResource and so on) work in
exactly the 
same way, whether the resources are in the resource fork or
the bundled 
resource file.
4. An OS X application cannot write to (i.e. alter) its own
resources. 
Apple has been discouraging this practice for many years and
has now 
made it illegal.

Robert P.
**************************************