Re: ColorSync Profile name length - Take 2
Re: ColorSync Profile name length - Take 2
- Subject: Re: ColorSync Profile name length - Take 2
- From: Nathan Duran <email@hidden>
- Date: Thu, 01 Sep 2005 22:41:45 -0700
> I guess the reason could be that the profile creation software (in
> this case ProfileMaker) is Carbon, not Cocoa, and/or using file
> manager libraries created for OS 9.
Cocoa is an application framework that sits on top of Carbon (as well as
CoreFoundation and some other, newer APIs). It does not provide very much
functionality that does not exist in Carbon-just an object oriented
abstraction layer to make application developers' jobs easier-and in many
cases, Carbon continues to provide functionality that does not exist in
Cocoa. Amazingly few large scale "flagship" apps are written in Cocoa for a
wide variety of reasons that are well beyond the scope of this mailing list.
The long name and Unicode supporting FSRef data type has been an integral
part of Carbon since the beginning, and was one of the primary things Apple
evangelized to developers following the NeXT buyout. I believe any OS after
8.1 technically supports long filenames so long as CarbonLib is present and
the volume is formatted as HFS+, but the Finder did not know what to do with
them until 10.0, so they were basically impossible to use. Certain
components of the OS like QuickTime and ColorSync never made the transition
to FSRefs, for what reason, I do not know.
But yes, they more than likely are still worried about supporting OS 9 given
the rate at which the print industry likes to upgrade their software, and
they probably don't want to write a new branch that uses the new stuff until
they have to. I generally find excessively lengthy file names difficult to
read anyway, so I can't say I blame them.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Colorsync-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden