Xcode 4 - ready to use? Also, console window behavior

Question

(Currently using Xcode 3.2, hesitantly switch to a newer version until it becomes stable and practical, but I'm going to start with new projects.)

Q. Is the Xcode 4 preview suitable for production work (that is, for the release of Mac / iOS applications), or should I wait until the final build is released?

Q1. I watched the Apple State of Tools WWDC video clip, where they talk in detail about the one-window approach to Xcode. I live and die with my console window. Is this window also integrated into the IDE window, or can I open the console window separately?

Thanks.

Answer 1

To answer your questions:

Q. Is the Xcode 4 preview suitable for production work (ie Mac / iOS release), or should I wait for the final build to come out?

You can evolve in Xcode 4 and move back and forth between Xcode 4 and 3 with the same projects. You must use Xcode 3.2 to submit to the App Store, but it is unclear whether this will be forced or simply errors in Xcode 4 may reject your application.

Mac applications do not go through the application store, so if they are built and deployed, you go away :) Be sure to thoroughly test your deployment platform just in case!

I live and die from my console window. Is this window also integrated in the IDE window, or can I get the console window displayed separately?

It is integrated. You can go to the debugger navigator, or you can "show the debugger area" in the view menu so that it appears under other areas of the navigator.

I cannot post images, but they can be seen at: http://i.stack.imgur.com/8A75R.png and i.imgur.com/hAjqx.png

About the general issues of stability / practicality: my experience is that the new design is really good. Everything is more logical. It still slows down the coding process when you adapt, but I dig a new Xcode and think that I will be faster with it in general.

There are errors, especially if you press the envelope. Using LLDB instead of GDB causes my computer to completely lock, for example: (

If you need to be productive and want to spend less time getting to the App Store right now, Xcode 3.2 is where you should be.

If you want to dampen around and can afford to spend time learning a new design and features when dealing with crashes, then Xcode 4 is very useful. Long-term, this is a big improvement in the current Xcode.

Answer 2

To detach the console as a separate window: (like DIY)

• Open a new window (Command + Shift + T)

• Hide the left panel and the utility panel if they are open (Command + 0 and Command + Alt + 0)

• Open the debug area (Command + Shift + Y)

• Drag the debug area until it covers the entire window, and then hide the toolbar.

There, you have a window that you can change or drag anywhere where only the console output is displayed. As in the good old days.

Answer 3

Yes, this is normal for HelloWorld projects, but I don’t think that Apple has anything like the required testing for usability and documentation.

Answer 4

First, you can set up a preview of Xcode 4 without replacing the existing version of Xcode; In fact, it will be installed in the same way as by default. Thus, you do not lose anything by trying it.

In my experience, the preview creates completely functional applications, but I often encounter problems with missing functions (either they moved to a place where I cannot find them, or they are not implemented yet), and occasional crashes that I returned to 3.2 for mine real work. The answers to this question show similar reactions of others.

I checked just now, and I could not find a way to disconnect the console or something else in a separate window, but I did not try very hard.

Answer 5

xcode 4 preview 6 pretty much sucks in terms of performance. the direction is excellent with many useful features, from the interface to the debugger and tools. however, it often crashes or the process freezes. For continuous and smooth development, I advise you to use xcode 3x. check out xcode 4 and enjoy the new features that go our way.

Answer 6

I just switched to XCODE 4 this week and I just like it. Of course, sometimes it crashes (well, it starts EVERYTIME at startup, but allows it to continue).

All the windows are there, and you have many options on how to lay them out.

The most impressive feature for me is how it is now related to compiler errors. I use VIM to edit my code - as soon as I write a file, XCODE compiles it and shows me any errors (I don’t need to “build”). Even nicer is that now it also has a button for switching from error to error, and not to painfully scrolling to red lines.

And the crash in my application is now just WONDERFUL. With each failure, an exact line of C code that crashed is displayed, and all local variables at that point in time are displayed. Brilliant!

Yes, it's a little buggy and crashes or freezes from time to time. But seriously, in just a couple of days I really don't want to come back.