>> Additionally - there would be no need for a 'toolbar' had apple left
>> the 'Apple menu' alone. As it provided EXACTLY this functionality
>
>No, they do completely different things--For instance, the tool bar in
>the window I'm writing this email contains a send button, a button that
>toggles between reply and reply-to-all, an attachment button, a fonts
>button, a colors button, an address-book button, and a save-as-draft
>button. None of those buttons are in the Apple menu of any version of
>the Mac OS.
while that is correct - they are not in the apple menu, and this would
not be the place for them. As hese functions are specific to the
application you are using.
HOWEVER all of the functionallity of the toolbar buttons you have setup
are *already* in
the application's prmary menubar!!!! And they are probably more eaily
accessable via key commands than a mouse anyway.
>In the Finder, very few of the buttons there duplicate anything that is
>in any version of the Apple menu in the Mac OS.
>
>> again ex: the 'view' button object for the tool
>> bar duplicates - inexactly - the primary menubar functionality of the
>> view menu, as the menu bar functionality is greater (various options
>> for
>> sorting, and icon size etc) than the toolbar button.
>
>The View menu is not the Apple menu.
my statement was meant to be read as:
"The toolbar does nothing but duplicate functionallity already existing
else where, as an example. the view buttons..."
The functionallity of the toolbar buttons - *should be* in the
(application's) primary menubar, and in all cases I have seen - does not
mean that there are not cases i have not seen - this is, indeed, the case.
The application of a function (using setting views as an example) should
in every case be placed in such a way as to reflect the scope of the
action. In the finder, this means placing the 'view settings' in the
primary menubar, as this action (setting the window view preference)
applies to all containers (folders/windows).
Just as the functionality of "save as jpeg" applies to a photoshop
document, and is only scoped to a document in photoshop. The function of
'paint can' (in photoshop) can only be applied to a specific document's
object/area, therefore it's functionality is kept at a lower level, the
tool palette - who's functionality is scoped to the objects/areas of one
single document.
again - winblows viloates this tenate of UI, with the (identical) menubar
inserted into every window. in the MS case this violation is more
agreegious(sp?) since unlike th etoolbar the menubar in every window can
not be turned off.
-------------------
Chip Scheide Systems Coordinator
Children's Hospital of Pittsburgh
"And as a man, who is attached to a prostitute,
is unfitted to choose or judge of a wife, so any
prepossession in favour of a rotten constitution of
government will will disable us from descerning a good one."
Thomas Paine - Common Sense, Feb 14 1776
___________________________________________________________________________
To unsubscribe send a mail message with a SUBJECT line of "unsubscribe" to
<[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
