Re: Xcode - An Apple Embarrassment
Re: Xcode - An Apple Embarrassment
- Subject: Re: Xcode - An Apple Embarrassment
- From: Thomas Clement <email@hidden>
- Date: Thu, 01 Mar 2012 11:36:33 +0100
I totally agree with you Matt.
Not being able to quickly access documentation from code is a major pain :(
Thomas
ps: I have filed a bug report long time ago about this but nothing has changed.
On Feb 29, 2012, at 11:13 PM, Matt Neuburg <email@hidden> wrote:
> On Wed, 29 Feb 2012 00:09:36 -0800, Joar Wingfors <email@hidden> said:
>>
>> On 28 feb 2012, at 22:26, Lee Ann Rucker wrote:
>>
>>> Plus there's no [...] jump to documentation.
>>
>>
>> Is too!
>>
>> Option+DoubleClick
>
> *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.
>
> Compare simple Option-click. It brings up the hated Quick Help pop-up, but at least if you then click on the tiny "book" icon you are shown *the actual documentation* on the clicked term. What is wanted is a simple *direct* way to do *that* (without the intermediate clicking on the tiny book icon). That is what Xcode 3 used to do.
>
> Also, reverting to Option-double-click: if this search word is a method name with multiple parameters, it enters the term incorrectly so it's useless. For example:
>
> - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
>
> Option-double-click on "application:" and it wrongly enters "application" in the search field, when it should be "application:didFinishLaunchingWithOptions:". Pretty lame, eh?
>
> <wildAndCrazy>
>
> 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:
>
> (1) Apple employees are right there on the spot, in the same building as the people who write Xcode, so if they really needed to get work done with Xcode they'd insist on having those problems solved.
>
> (2) Watch the WWDC 2011 videos *carefully* and look at how the presenters interact with Xcode 4. They encounter bugs all the time and either skip past them or are stymied by them. This makes me think they are not familiar with or dependent on Xcode in their real lives.
>
> :)
>
> </wildAndCrazy>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden