Re: Type/Creator codes
Re: Type/Creator codes
- Subject: Re: Type/Creator codes
- From: Ali Ozer <email@hidden>
- Date: Sun, 13 May 2001 11:10:35 -0700
Folks, there are many people on this list who are here to try to answer
questions and help developers, but extended discussions just get in the
way. If you have good ideas, sending them to the various feedback
addresses will be the best way to assure they get seen.
Given my first message wasn't super clear, and given where things are on
10.0, here's what you can do in your applications:
1. Use extensions to assure that files are not fragile with regards to
being placed on the web or alternate file systems, and sent to other
platforms.
2. Use Mac OS file types to assure that files are not fragile with
regards to name changes.
3. Don't use Mac OS file creators as the strong-binding they establish
isn't always appropriate. But, if your document needs a creator code to
open properly on Mac OS 9, and it needs to open properly on Mac OS 9,
then by all means, include it.
There are issues with using file extensions, and there are issues with
using Mac OS file codes, and we are looking at allowing users to name
documents as they please and reducing fragilities associated with file
typing.
The original question was, how to read/write type codes in Cocoa. Some
good suggestions have been posted. I'll add that in 10.0, there is a
Cocoa API to get the Mac OS file type from a document; in addition, you
can specify Mac OS files types in the open dialog, and in various APIs
which open files based on extensions. These can be used to deal better
with extensionless documents.
Ali