Re: "untitled" vs "Untitled"
Re: "untitled" vs "Untitled"
- Subject: Re: "untitled" vs "Untitled"
- From: John Stiles <email@hidden>
- Date: Sun, 10 Jul 2005 12:09:36 -0700
On Jul 10, 2005, at 11:55 AM, Carlos Salinas wrote:
On Jul 10, 2005, at 11:32 AM, John Stiles wrote:
Actually, this kind of reminds me of how many controls still
behave differently between Carbon and Cocoa--just as one example
that I have handy, try holding the mouse button down and scrubbing
over the tabs in a tab control. In Carbon it behaves like a button
(only the tab you originally clicked will receive clicks) but in
Cocoa it lets you scrub between all the tabs with the button held
down. (rdar://2778946 ... filed in September 2001, still unfixed!)
I don't have the HIG in front of me so I am not certain which way
is more "correct," but I suspect the HIG doesn't leave the
question unanswered.
The thing that bothers Cocoa engineers (and those with a NeXTSTEP
background) is the assumption that the old Mac way is the right way
to do things. This is the assumption that if Cocoa does it
differently then its a bug in Cocoa, not in Carbon.
In some ways the NeXTSTEP user interface was better than the Mac
user interface. For example, NeXTSTEP did a much better job
handling multiple applications and multiple windows (the dock, open
file icons along the bottom, ways to reorder windows, actually
showing the window when it was dragged, etc). NeXTSTEP also
eschewed modal dialogs and used modeless inspectors, which are
quite common on OS X today. NeXTSTEP apps tended have a lot more
WYSIWYG aspects - such as when you dragged a box in a graphical
editor, you actually saw the box move, not a dotted outline. In
general the NeXTSTEP interface was a lot more liberal, a lot more
freeing than the Mac interface. Some of that has carried forth in
Cocoa applications. For example, Cocoa apps tend to let you copy
value text fields, even the text in the About panel can be copied.
The Finder, however, still prevents copying value text fields in
the inspectors. The user has to manually transcribe that
information if they need it elsewhere.
So anyway that's the thing with Cocoa engineers. Some Cocoa things
are better, some old Mac things are better.
I think you're missing my entire point.
The goal of an engineer should not be to implement what they
personally think is the "best." The goal should be to implement the
HIG perfectly.
If the HIG is sub-standard, then talk to the authors and get it
fixed! Obviously there have been a lot of NeXT-themed ideas added to
the HIG already. Once the HIG is fixed, everyone benefits--Carbon,
Cocoa, and third-party developers. And if the HIG authors don't like
your idea, the engineers need to respect their judgement. The HIG is
what makes a Mac a Mac. (Obviously it's not the CPU :P )
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden