• 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: Xcode - An Apple Embarrassment
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode - An Apple Embarrassment


  • Subject: Re: Xcode - An Apple Embarrassment
  • From: Wade Tregaskis <email@hidden>
  • Date: Wed, 29 Feb 2012 16:41:27 -0800

> *No*. I've said it before (right here) and I'll say it again; this is *not* jumping to the documentation, and it is *not* doing what Xcode 3 did. It switches to the documentation window and it enters the double-clicked word into the search field, and it does the search, but it ****doesn't display the actual documentation**** on the double-clicked word.

Indeed, the regressions around this simple piece of functionality are disturbing.  I also find that it rarely handles double clicks correctly.  I have to triple or quadruple-click much of the time.  It's often faster to just bring up the organiser (command-shift-2, obviously) and navigate to the desired docs directly, than play some kind of bizarro skill game with my mouse button.

> Once again I put forward my pet wild-and-crazy "dog food" theory that the people at Apple do not actually *use* Xcode for serious work. I know it sounds wild and crazy, but I have two kinds of evidence for this theory:

Occam's razor (and my own nearly four years working on developer tools at Apple) will present a different explanation:  Xcode is used exhaustively within Apple, but the Xcode team just aren't good at producing a solid product.  I'm not sure why that is; all the people I know on the Xcode team are very good developers, at least individually.

Someone else pretty well hit the nail on the head earlier when they suggested that developer tools just aren't given much top-level interest.  I don't know if that can be blamed for the end result though.
_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


  • Follow-Ups:
    • Re: Xcode - An Apple Embarrassment
      • From: Alex Zavatone <email@hidden>
References: 
 >Re: Xcode - An Apple Embarrassment (From: Matt Neuburg <email@hidden>)

  • Prev by Date: Re: How are views supposed to reload after being nillified by memory warnings?
  • Next by Date: Re: How are views supposed to reload after being nillified by memory warnings?
  • Previous by thread: Re: Xcode - An Apple Embarrassment
  • Next by thread: Re: Xcode - An Apple Embarrassment
  • Index(es):
    • Date
    • Thread