Re: Does anyone else dislike Xcode 4?
Re: Does anyone else dislike Xcode 4?
- Subject: Re: Does anyone else dislike Xcode 4?
- From: Alex Kac <email@hidden>
- Date: Sun, 24 Jul 2011 20:31:59 +0200
On Jul 24, 2011, at 8:22 PM, Jeffrey Oleander wrote:
>> Alex Kac <email@hidden> 2011-07-24 13:07 wrote:
>> ...its a one window interface...
>
> This is a deal killer. Seeing things next to each
> other is vital. It's the reason we had to chop
> down so many trees in the olden days, for highly
> cross-referenced listings (even with tiny little
> laser print shrinking 2 older green-bar listing
> pages to one 8.5" by 11") to stretch out across
> conference tables next to each other.
OK so Xcode can do that. Turn on the assistant, and click on a file to open. Then option click on another file. Bam - two columns. Or CTRL-SHIFT-COMMAND on a file and you get this nice HUD that lets you pick whether to open the file in a new window, in a second column, or a third part of the window.
The problem is most people go into Xcode 4 and never bother to learn how it works. The above is one major reason I'm so much more productive in Xcode 4. I am always using the two column view in Xcode 4. And sometimes I have 3-4 windows open on my multi-monitor 27'' Mac.
Xcode 4 makes all of that 10x easier than Xcode 3 did.
>
>> Yes it did take some time to get used to it and
>> relearn how to do basic things. At first I hated
>> Xcode 4's way of dealing with libraries because
>> I'd spend literally days trying to get it to
>> link static libs that used to be a breeze in
>> Xcode 3. Its not a matter of "computer should
>> deal how I work and not me learning how it works"
>> because in the first place we learned how Xcode 3
>> worked, not how we worked and this is engineering
>> after all.
>
> OTOH, some of us have been linking static and
> dynamic libraries since the 1970s and it was
> straight-forward enough back then that we could
> teach 70 year old mechanical engineers how to do
> it, so why should we have to stand on our heads
> and sacrifice pigeons to get it to work, now?
I've been doing it since 1990. Not as long as the 70s, but still. The problem is that Xcode 4 does it more automatically and the options in are a different place. I admit it took me a lot longer to figure this out than it should've, but once its figured out it wasn't hard (the problem was that the lib path was set to the project dir, not the build dir which is a 3rd pane in Xcode and yes, a major bug in the UI/logic and one I've filed a radar on).
>
>> All that rambling to say that just like Lion,
>> just because its different doesn't mean its bad.
>
> Right. Back to dev talk.
This post is my last word on the subject. Anything else I write would be just be more of the same._______________________________________________
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