Re: Mac OS X 10.1 File Name Extension Guidelines
Re: Mac OS X 10.1 File Name Extension Guidelines
- Subject: Re: Mac OS X 10.1 File Name Extension Guidelines
- From: Rosyna <email@hidden>
- Date: Thu, 13 Sep 2001 19:52:41 -0700
Don't want this to become a huge rant.
Exactly why extensions are no good. When you run IE (everytime) it
switches .html extension to be opened with IE. if it had a creator
code, IE could not do this. Same goes for .txt files. Genius AIM
programmers decided all .txt files should open in AIM.
And BOTH creator code and extensions can be overridden by the finder in OS X.
Ack, at 9/13/01, Piers Uso Walter said:
You're only talking about yourself. What about others who may want
to open these files?
The most obvious problem of the current creator code based
application binding policy is that it almost never does what you
want when you work on somebody else's files, e.g. file that you
receive via email or files in a different user account that you want
to open.
I don't want any text files to open up in SimpleText or BBEdit, just
because they may have been created with those tools (I'd prefer to
use TextEdit).
I don't want PDF files to open up in my Acrobat Reader, just because
they may have been distilled by Acrobat (I'd prefer to use Preview).
And most certainly I do not want any HTML file to launch my Internet
Explorer, just because its creator type says so (I'd prefer to use
OmniWeb).
All of this happens to me *daily*, though, which is so annoying that
I can't even begin to describe it. This ill-conceived behavior
prevents me from using a simple double-click to open files, forcing
me to always drag the files to the application that I want to use,
which again forces me to keep all of these apps in the dock, for the
slight chance that I may have to drag a file to them. This really is
the opposite of intuitive and user-friendly.
--
Sincerely,
Rosyna Keller
Technical Support/Holy Knight/Always needs a hug
Unsanity: Unsane Tools for Insane People