Re: Does anyone else dislike Xcode 4?
Re: Does anyone else dislike Xcode 4?
- Subject: Re: Does anyone else dislike Xcode 4?
- From: JongAm Park <email@hidden>
- Date: Mon, 25 Jul 2011 10:55:32 -0700
On Jul 25, 2011, at 10:42 AM, Nick Zitzmann wrote:
> On Jul 25, 2011, at 10:02 AM, JongAm Park wrote:
>
>> I don't know how this thread was started but, yeah, I don't like the Xcode 4.
>>
>> The reason is :
>>
>> - Requires too much scree real-estate
>> Also, waste of screen real-estate
>
> Just like Visual Studio, Xcode 4 works best when it's running as a full screen app. So yes, this is a problem under Snow Leopard, but if you try running each project in its own space under Lion, I think you'll like it better. I certainly did.
>
That is one thing, but generally, it doesn't apply.
>> - Different shortcut from those of Xcode 3
>
> That just requires some retraining.
Yes and No. Usually shortcuts in Mac are made of first or at most the second letter of the menu item string.
However, Xcode 4 broke that. Also, if it was not with Xcode 3 ( there are some cases ), Xcode 4 changed that also.
>
>> Annoying bugs :
>>
>> [Bug 1]
>> I reported this yesterday, but try to put an NSPathControl on an instance of NSWindow ( resource editor )
>> Make sure if your project is to be built for 10.6, for example.
>> It will throw an error message saying that "NSPathControl and NSPathControl cell are not available in Mac OS X prior to 10.5"
>>
>> [Bug 2]
>> Prints out many Warning message saying that this and that property of widgets are not supported in Mac OS X prior to 10.5.
>> Again, just like the Bug 1 case, the project is not built for pre-10.5
>
> Those two aren't bugs. I don't know why, but nibs actually have separate deployment targets from the rest of the project. If you update the deployment target in each nib, which you can do in the file inspector, then the warnings should go away.
>
I already know that and it is set as such.
>> [Bug 3]
>> Lots of memory usage
>> - Just open Xcode 4.2, for example. Don't use Xcode 4 and just leave it as it is.
>> - It will start to use lots of memory ( thus eats more HDD space due to increase of VM size or swap files. )
>> ( Is this because Xcode provide more features? I don't think so. )
>
> Pretty much every version of Xcode has used a lot of memory, so this isn't too surprising.
>
Also, it doesn't apply here.
I monitored how Xcode 4 used memory for long time, and I know things by experience.
If Xcode 4 provides more features which require more memory, it is OK and understandable.
But look here. It just stays there without doing anything. ( indexing? no. )
But it starts to eat up memory more and more.
>> [Bug 4]
>> Error/Warning of previous built remains there sometimes. So, although it says "Successfully built", it also shows red/yellow error/warning message.
>> => this confuses a lot.
>
> Xcode 3 did this as well if you had multiple projects open at once, and one of which was a sub-project of another, and you built the sub-project which generated errors or warnings, and you fixed them, and then built the master project. I never tried that in Xcode 4 because Xcode 4 treats sub-projects as extensions of the master project.
>
I'm not talking about that kind of case.
_______________________________________________
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