• 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: Scott Anguish <email@hidden>
  • Date: Sun, 9 Sep 2001 00:40:32 -0400

On Saturday, September 8, 2001, at 06:32 PM, Peter Ammon wrote:

> 2) De-emphasize the importance of file name extensions; they're an
> option for an application, but not a recommendation.
>
> 3) Most importantly: provide an API to map type/creator codes to
> filename extensions, and use that API in applications such as Mail or
> Fetch that would potentially transfer files to a machine that relies on
> filename extensions.


Fetch, Mail are just two examples.. then lets look at the raft of
NON UI stuff

cp
ncftp/ftp/ftpd
apache
mv
scp, ssh
perl

virtually ALL of the raft of unix and open source utilities would
be subjected to this.

at that very point, you're back to OS 9 as far as
compatibility/portability goes.


  • Follow-Ups:
    • Re: Mac OS X 10.1 File Name Extension Guidelines
      • From: Peter Ammon <email@hidden>
References: 
 >Re: Mac OS X 10.1 File Name Extension Guidelines (From: Peter Ammon <email@hidden>)

  • Prev by Date: Re: Mac OS X 10.1 File Name Extension Guidelines
  • Next by Date: Programmatically connecting to first responder
  • 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