Content deleted Content added
Guy Harris (talk | contribs) Consistently use "file system" rather than "filesystem". |
Guy Harris (talk | contribs) →Operating system handling: Rewrite to make it clearer that it's the use of extensions, rather than the use of type and creator codes, in macOS that stems from its UN*X origins. |
||
Line 26:
With the advent of [[graphical user interface]]s, the issue of file management and interface behavior arose. Microsoft Windows allowed multiple applications to be [[file association|associated]] with a given extension, and different actions were available for selecting the required application, such as a [[context menu]] offering a choice between viewing, editing or printing the file. The assumption was still that any extension represented a single file type; there was an unambiguous mapping between extension and icon.
The [[classic Mac OS]] disposed of filename-based extension metadata entirely; it used, instead, a distinct file [[type code]] to identify the file format. Additionally, a [[creator code]] was specified to determine which application would be launched when the file's [[Icon (computing)|icon]] was [[double-click]]ed. [[macOS]], however, uses filename suffixes
== File system support ==
| |||