On Apr 18, 2011, at 7:04, G S wrote: Have you read the HIG and looked at other apps?
> The user does not know in advance how a UI element has been implemented, nor should he be expected to. That's why view options belong under the View menu.
>
So as view options belong under the View menu, where do you think an action to get a particular WINDOW belongs?
How do you know in advance that it's a window? You're asking the user to memorize which of an application's visual elements are windows, and which are not. Ridiculous.
> For example, if I'm using an audio application and want to show some meters, am I supposed to guess whether those meters have been implemented as a separate window or an integrated pane? That's why options like that go under View.
Very, very bad example, as it's wrong. Usually those won't be in View, usually those are tools that go into some kind of Tools menu. They're usually in utility windows or something. The Windows menu contains normal windows, usually no utility windows.
You should probably use a few more Mac apps before you call somebody else wrong. But why take my word for it? Let's look at a classic Mac application, Photoshop. Here's the Window menu in CS5:
http://farm6.static.flickr.com/5028/5630390118_05aaf59259_b.jpgWhat do you know: It's chock full of exactly the kind of things I'm talking about.
I thought you were talking about open windows? This is not at all like that. Moreover, this is an Adobe app, it's wrong at many levels, if you think that should be an example...
First of all, I am talking in general, one example is no statistics, and it also doesn't say that if an app (even an Apple app) does something than it does it right. I know many examples of (Apple) apps that do things against the HIG.
And also, a "welcome window" is never supposed to be a utility window.
Exactly, which is why it shouldn't have application controls in it.
That's a different question, I am talking about the question how you can get back the welcome window, not about what it contains.
Christiaan
|