• 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: Mac OS X 10.1 File Name Extension Guidelines
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Mac OS X 10.1 File Name Extension Guidelines


  • Subject: Re: Mac OS X 10.1 File Name Extension Guidelines
  • From: Brent Gulanowski <email@hidden>
  • Date: Tue, 11 Sep 2001 19:09:48 -0400

> From: Andreas Monitzer <email@hidden>
> Date: Tue, 11 Sep 2001 14:16:45 +0200
> To: email@hidden
> Cc: (Cocoa-Dev) email@hidden
> Subject: Re: Mac OS X 10.1 File Name Extension Guidelines
>
> I think I've read that Mac OS X already does content-based mapping as a
> last resort (see that USENIX article by Wilfredo Sanchez).
>
> andy
> --
> Discussion forthcoming.


So why is my system littered with files typed as generic "document"? I hate
that, partly because it's non-descriptive, but mostly because it means that
double clicking it won't open it. Usually I know what type it is from name
and/or location, but the Finder/OS is too dumb to know that my clicking it
means I want to open it and that _some_ app should damn well try 'cause I
said so!

bg


References: 
 >Re: Mac OS X 10.1 File Name Extension Guidelines (From: Andreas Monitzer <email@hidden>)

  • Prev by Date: Re: opposite of OOP (was file extensions)
  • Next by Date: file - open recent
  • Previous by thread: Re: Mac OS X 10.1 File Name Extension Guidelines
  • Next by thread: Re: Mac OS X 10.1 File Name Extension Guidelines
  • Index(es):
    • Date
    • Thread