Re: Type/Creator codes
Re: Type/Creator codes
- Subject: Re: Type/Creator codes
- From: "Ricky A. Sharp" <email@hidden>
- Date: Sun, 13 May 2001 09:22:03 -0500
on 5/13/2001 8:38 AM, Dave Horlick at email@hidden wrote:
>
> 2. I have no immediate visual feedback on what to expect when I
>
> double-click a file
>
>
What about *the icon*?
>
>
> This is a classic example where Classic Mac OS wanted to be smarter
>
> than I am (the very characteristic that made Classic Mac OS mostly
>
> annoying for me), and miserably failed.
>
>
I imagine that some Mac users (even some who subscribe to the cocoa-dev
>
mailing list) may appreciate not having to maintain a dozen extension
>
codes in their head at all times. You always have the option of going in
>
and deleting a file's creator code. Admittedly, it would be nice if
>
their were a user-friendly way to do this.
>
>
I agree that creator codes don't work well for pictures, text files,
>
hypertext markup, and rich text documents. But what about all the
>
proprietary binary formats? Is it really such a transgression for
>
Reunion to put a creator code on a family tree file?
Exactly. Each scheme has its place.
I don't see it as one scheme ever replacing the other. There are situations
where you can use both.
My apps are meant to be installed on HFS/HFS+ volumes. I don't use
extensions at all. If I wanted to have my apps be volume-agnostic, I would
migrate to extensions. But staying on HFS/HFS+, type and creator are very
powerful things.
------------------------------------------------------------
Ricky A. Sharp Instant Interactive(tm)
Founder & President
email@hidden
http://www.instantinteractive.com
------------------------------------------------------------