Creator code
This article possibly contains original research. (January 2019) |
A creator code is a mechanism introduced in the
Creator codes are four-byte
The binding are stored inside the
The key difference between extensions and Apple's system is that file type and file ownership bindings are kept distinct. This allows files to be written of the same type - TEXT say - by different applications. Although any application can open anyone else's TEXT file, by default, opening the file will open the original application that created it. With the extensions approach, this distinction is lost - all files with a .txt extension will be mapped to a single text editing application of the user's choosing. A more obvious advantage of this approach is allowing for
macOS retains creator codes, but supports extensions as well. However, beginning with Mac OS X Snow Leopard, creator codes are ignored by the operating system. Creator codes have been internally superseded by Apple's Uniform Type Identifier scheme, which manages application and file type identification as well as type codes, creator codes and file extensions.
To avoid conflicts, Apple maintained a database of creator codes in use. Developers could fill out an online form to register their codes.[2] Apple reserves codes containing all lower-case ASCII characters for its own use.
Creator codes are not readily accessible for users to manipulate, although they can be viewed and changed with certain software, most notably the macOS command line tools GetFileInfo and SetFile which are installed as part of the developer tools into /Developer/Tools.
See also
- Type code
- Uniform Type Identifier
References
External links
- How application binding policy changed in Snow Leopard
- Szekely, Ilan (Aug 2003). "Type/Creator Database" (Excel). Retrieved 2017-02-11.
The developer acknowledges that since the information was manually accumulated from various sources, some not registered with Apple, from various apps and their files, validity is NOT guaranteed