Re: Does anyone else dislike Xcode 4?
Re: Does anyone else dislike Xcode 4?
- Subject: Re: Does anyone else dislike Xcode 4?
- From: Nick Zitzmann <email@hidden>
- Date: Mon, 25 Jul 2011 11:42:25 -0600
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.
> - Different shortcut from those of Xcode 3
That just requires some retraining.
> - Useless tool bar
True.
> 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.
> [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.
> [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.
[…]
> However, my point is why they give up "already working, better" approach delivered by Xcode 3? To people who uses "All-in-one" configuration only, they would think that "Xcode 4 is same to Xcode 3!". But.. no. I have used its compact layout more, because it was more flexible especially when I needed to work with multiple projects.
This is my main grievance with Xcode 4 as well, and really, it's the second time this has happened. The original Project Builder had an all-in-one view, and developers complained, so they added a CodeWarrior-like condensed view to Project Builder 2, only to take it out of Xcode 1. Developers complained again, and the condensed view came back in Xcode 2. Now it's gone again. Maybe if enough people complain about it, it'll come back in Xcode 5, I don't know… Every other major IDE uses an all-in-one view.
Nick Zitzmann
<http://www.chronosnet.com/>
_______________________________________________
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