{#}  Replies are directed back to [EMAIL PROTECTED]
{#}  To reply to the author, write to B Keyport <[EMAIL PROTECTED]>

>There is a reason that Apple leads the industry.

Apple don't lead except in the "Macintosh" industry.

What Apple has lead in, is *USER CONTROL* - the user has 
traditionally had full control over everything in their system, 
either through modification of preference files, or resedit hacking 
up menu files, whatever.


>From the proverbial Day One, Macintosh applications have been designed to
>operate in a coherent fashion.  The design philosophy revolved heavily
>around the concept of learning one application and learning several.  Learn
>how to control the clipboard, print, or save a file in one application, and
>you've pretty much learned how to do the same thing in all of them.

Yes, true.

>Apple has collected these design ideals together into the Human Interface
>Guidelines.  The HIG specify how windows should be laid out, what the
>standard keyboard shortcuts are, how an application should respond when its
>icon is clicked in the dock, and how controls should be laid out in a
>window.  It specifies that the default button in a dialog box should be
>bound to the Return key.  It specifies that after the Apple and application
>menus, a program should have File, then Edit menus.  It specifies that new
>windows open in front of other windows.

And that specification is flawed, user annoying, and WILL cost apple.

>All this adds to a sense of stability and comfort when working with
>applications.  They behave in a predictable manner.  One doesn't have to
>recall which application in which one is working before being able to recall
>the keyboard shortcut for copying the selection to the clipboard -- it's
>Command-C, not Control-C, Alt-C, Fn-Y, or F7.

... and a sense of annoyance when it comes to windows popping up in 
front of other applications.
>
>It is the intent of the Fire Development Team to make Fire one of the
>flagship products of OS X.  As such, we will adhere to the HIG as closely as
>possible.

Adhering to the HIG does not exclude expanding the rules of the HIG 
outside of defaults.

>  Causing a new chat window to appear behind another window at all
>is a stretch of the HIG, but I realize that it can be irritating to have to
>waste those five seconds while bringing back the window you were typing in
>and picking up where you left off.  As such, I concede that having a new
>window pop up behind an existing, actively-used window is preferable to
>arbitrarily bringing that new window in front of the window you're using,
>but it is poor application design to arbitrarily never open a chat window in
>front.

It is worse application design to be braindead and strictly stick to 
the HIG. I view most of the HIG as the same as most electricians view 
the NEC - Minimum standards. You can expand on it, as long as you 
don't violate it. Allowing new windows to pop up behind existing 
windows in *all* cases is not violation of the HIG, as long as it's 
not the default.

>Fire is open-source software.  If you disagree with a design element, you
>have every right to modify the code to your heart's content.  But I refuse
>to intentionally design Fire to operate counter to the operation of every
>other Macintosh application out there.

All I'm asking for is an *option* to expand the HID, to match the UID Spec.

To heck with the Humans, the Users rule the interface.

Thank you.
-- 

{#} ----------------------------------------------------+[ fire ]+---


Reply via email to