• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Type/Creator codes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Type/Creator codes


  • Subject: Re: Type/Creator codes
  • From: Dave Horlick <email@hidden>
  • Date: Sun, 13 May 2001 09:38:53 -0400

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?

Dave


  • Follow-Ups:
    • Re: Type/Creator codes
      • From: "David W. Halliday" <email@hidden>
    • Re: Type/Creator codes
      • From: Scott Anguish <email@hidden>
    • Re: Type/Creator codes
      • From: Uli Zappe <email@hidden>
    • Re: Type/Creator codes
      • From: "Ricky A. Sharp" <email@hidden>
References: 
 >Re: Type/Creator codes (From: Uli Zappe <email@hidden>)

  • Prev by Date: Re: Type/Creator codes
  • Next by Date: Re: Type/Creator codes
  • Previous by thread: Re: Type/Creator codes
  • Next by thread: Re: Type/Creator codes
  • Index(es):
    • Date
    • Thread