Re: Xcode 4 related questions
Re: Xcode 4 related questions
- Subject: Re: Xcode 4 related questions
- From: Joar Wingfors <email@hidden>
- Date: Sat, 12 Mar 2011 20:36:21 -0800
On 12 mar 2011, at 15.00, Nathan Sims wrote:
> That's wholly disingenuous. The problem is in transitioning from Xcode 3, most things in Xcode 4 require A LOT of discovering, as the entire paradigm has changed and it's not apparent from the UI where everything is or how everything is set up to work. Xcode 3 was simple: for the basics of building/debugging/running, everything was right there on the GUI in plain sight. That's a good UI design. Xcode 4 imposes a UI workflow on things that you must discover before you can be productive with it.
I would pose that Xcode 3 only seems simple to you because you've used it for some time already. Conversely, Xcode 4 probably appears more convoluted to you than what it really is because you're trying to make it work just like Xcode 3.
On 12 mar 2011, at 15.29, Nathan Sims wrote:
>>> Me too, but if there's a way to make the UI useful, I don't see how yet. A lot of visibility into the build process seems hidden now.
>>
>> Which parts of the build process? We expose all of the same control over the build process, and the same amount of feedback over what's going on during a build. Some things have moved around a bit though, such as...
>
> My basic workflow when developing is:
> a. Simultaneously Edit numerous files, then Compile (do this many, many times!)
> b. Build
> c. Usually (95%) go back to a.
> d. Finally, Run. Then go back to a.
>
> Xcode 3 made this easy, as the steps above just entailed a click on a button already present on the UI. I'm not alleging that Xcode 4 can't do this, but it's not obvious to me where the compile or build without running buttons are, or how to have numerous free editing windows up, or how to have the Build results window up so I can reference it while editing numerous files, etc. The Xcode 4 GUI seems to have a more 'single-threaded' workflow mindset.
One of the hallmark features of Xcode 4 is "fix-it", that provide "live" warnings / errors as you write your code. With this in mind, your workflow in Xcode 4 will be reduced down to:
[1] Write code
[2] If fix-it shows warnings / errors, goto #1
[3] Build & Run
I have no doubt that lots of developers have trained themselves to hit Cmd+K / Cmd+B all the time (and the keyboard shortcut for Build is unchanged in Xcode 4 for this very reason), but it doesn't really make as much sense any more.
On your other questions: I'd encourage you to review the training & reference material that we're providing you with. Xcode 4 is not the kind of release that you necessarily should expect to just switch over to and immediately find your way around. This is a bigger release than what the +1 version number would otherwise indicate, and we can't help there being a bit of a learning curve.
If you haven't already, I'd also encourage anyone interested in getting up and running with Xcode 4 to also check out the developer forums:
<http://developer.apple.com/devforums/>
Many questions that are being discussed here on Xcode-Users have already been discussed there (while Xcode 4 was still in beta), and solutions and workarounds have often times been provided already.
Best,
j o a r
_______________________________________________
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