• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: "untitled" vs "Untitled"
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: "untitled" vs "Untitled"


  • Subject: Re: "untitled" vs "Untitled"
  • From: John Stiles <email@hidden>
  • Date: Sun, 10 Jul 2005 11:32:18 -0700

On Jul 10, 2005, at 8:44 AM, Ali Ozer wrote:

At this point use of "untitled" vs "Untitled" is more of an aesthetic question, and (to bring the discussion back to Cocoa- land) NSDocument uses a naming convention with capitalization familiar to users of Adobe and Microsoft apps. By sticking with NSDocument's default behavior, your apps will have leverage of any change that might happen in the guidelines and frameworks. But if you want to use "untitled," you are free to do so, since I believe the hooks exist in NSDocument.

Maybe Engineering disagrees internally with the HIG in some places. That's natural. But until the HIG is actually changed, isn't it Engineering's job to follow it to the letter? I don't agree with the sentiment that "well, we thought this part of the HIG could use some work, so we ignored it and did something a little different instead." It's bad enough when third parties do it, but when the application frameworks do it, that can cause serious inconsistency. I mean, Carbon and Cocoa are on parallel development tracks with different developers, but they're both trying to conform to the same HIG, right? This makes inconsistencies stand out even more, because every time one team deviates from the HIG, that's one more thing users can notice and say "oh look, Carbon apps do this wrong" or "Cocoa apps don't do such-and-such like a standard Mac app does." We've all heard it before, right? :)


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. However, it seems like sometimes Engineering implements what they think the standard SHOULD be, not what it says. _______________________________________________
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
  • Follow-Ups:
    • Re: "untitled" vs "Untitled"
      • From: Carlos Salinas <email@hidden>
References: 
 >"untitled" vs "Untitled" (From: David Catmull <email@hidden>)
 >Re: "untitled" vs "Untitled" (From: Ali Ozer <email@hidden>)
 >Re: "untitled" vs "Untitled" (From: "Brian K." <email@hidden>)
 >Re: "untitled" vs "Untitled" (From: Ali Ozer <email@hidden>)
 >Re: "untitled" vs "Untitled" (From: m <email@hidden>)
 >Re: "untitled" vs "Untitled" (From: "Brian K." <email@hidden>)
 >Re: "untitled" vs "Untitled" (From: Ali Ozer <email@hidden>)

  • Prev by Date: Re: Documentation frustrations
  • Next by Date: Protocol compiler hint vs no hint....
  • Previous by thread: Re: "untitled" vs "Untitled"
  • Next by thread: Re: "untitled" vs "Untitled"
  • Index(es):
    • Date
    • Thread