Sadly Apple
went with the NeXT way of doing things with Mac OS X. There
seems to be very little of the Classic Mac OS in Mac OS X. While I think
that getting rid of resource forks is a good thing, was it really necessary
to drop the file creator attributes? Very frequently I have files of a
certain type .JPEG for example, where I want to open certain files of that
type with one program, and others with another. With the file creator
attributes this worked just fine. With the Microsoft & Mac OS X "one size
fits all" attitude, only one app will be associated with *ALL* files with
that extension.
Not on HFS+ filesystems -- I can still pick an individual opener for a
particular file under Get Info, even in 10.4.
I would think even a UFS filesystem could emulate that.
Where would you hide the creator attributes? Or, are you
uggesting a kludge workaround (e.g., change the "extension"
to something unique; build some middleware that consults
a user-maintained table of creator attributes; etc.)?