FACTOID # 13: The United States spends more money on its military than the next 12 nations combined.
 
 Home   Encyclopedia   Statistics   Countries A-Z   Flags   Maps   Education   Forum   FAQ   About 
 
 
 
WHAT'S NEW
RECENT ARTICLES
More Recent Articles »
 

SEARCH ALL

FACTS & STATISTICS    Advanced view

Search encyclopedia, statistics and forums:

 

 

(* = Graphable)

 

 


Encyclopedia > Creator code

A creator code is a mechanism used in pre-Mac OS X versions of the Macintosh operating system to link a data file to the application program which created it, in a manner similar to file extensions in other operating systems. Codes are four-byte OSTypes. For example, the creator code of the HyperCard application and its associated "stacks" is WILD. This allows the application to launch and open a file whenever any of its associated files is double-clicked.


The key difference between extensions and Apple's system is that file type and file ownership bindings are kept fully distinct. This allows files to be written of the same type - TEXT say - by different applications, and freely opened by any application that can read TEXT files, but when double-clicked, will correctly open the original application that created it. With the extensions approach, this distinction is lost - all files with a .txt extension may only be mapped to a single text editing application.


Mac OS X retains creator codes, but supports extensions as well. The deprecation of creator codes (and type codes) over the older extension system, popularised by DOS and others, has been very controversial with Mac users. The type and creator system is considerably richer and more sophisticated than that provided by extensions, and many users felt that adopting DOS conventions is a backward step. They claim that type and creator information rightfully belongs to the metadata associated with a file, and is therefore illogically placed within the file's name, where its presence can cause problems for the user. Apple defend the decision by saying that extensions have become the de facto standard for indicating file type, and they need to work seamlessly with the rest of the industry.


Creator codes are not readily accessible for users to manipulate, although they can be changed with certain software tools.


See also


  Results from FactBites:
 
Technical Note TN1134: The Preferences Problem (5300 words)
There is code at the end of this Note that shows how you might want to locate a preferences file by creator code and/or file name.
Always creating a preferences file makes for slightly simpler code, but since you have to be prepared to run even if you cannot create a preferences file, you might as well wait until you actually need to create a preferences file before dealing with those possible problems.
One of the easiest workarounds to this problem is to locate your preferences file by a unique creator code (your application's signature springs to mind), which allows the user to rename your preferences file and not affect your application at all.
  More results at FactBites »


 
 

COMMENTARY     


Share your thoughts, questions and commentary here
Your name
Your comments

Want to know more?
Search encyclopedia, statistics and forums:

 


Lesson Plans | Student Area | Student FAQ | Reviews | Press Releases |  Feeds | Contact
The Wikipedia article included on this page is licensed under the GFDL.
Images may be subject to relevant owners' copyright.
All other elements are (c) copyright NationMaster.com 2003-5. All Rights Reserved.
Usage implies agreement with terms, 1022, m