Following "Try it out" for the windowBasedApp. Unfortunately, Xcode 4 not only looks different than the Xcode 3 examples in the book, but Xcode 4 doesn't function like the Xcode 3 examples in the book.

Initially couldn't build the windowBasedApp. Found that "Core Data" which was not checked by default needed to be checked.

Now trying to do step #4 on page 85, dragging a View Controller onto the MainWindow.xib window. Can drag over to the window but upon release the View Controller scoots back to the library and nothing remains. How to make the View Controller stick?

I have a screenshot but there doesn't appear to be a way on this forum to attach a JPG.

How can the XIB window be brought up in list mode with Xcode 4? The book example on page 86, figure 4-13, shows a list not a graphic.

Thanks.

Had to do three things to make it work with Xcode 4.

Step #4, had to drag the View Controller object from the Object Library not to the center Window but all the way to the Window object in the column of objects in the second pane from the left, with the stack of objects, File Owner, etc.

Step #9, had to manually enter the NIB name. The drop-down list was inexplicably empty.

Step #11, inside method "didFinishLaunchingWithOptions", had to addSubview using "_window" not simply "window".

I can understand Apple making functional improvements to Xcode, from 3.6 to 4.0, but these differences don't make any sense at all.

A few points-
Core Data should not be checked. It is not used.
Concerning step #4
The window in the workspace is not the "MainWindow.xib", it is the UIWindow. The gutter area (Dock) to the left of the workspace serves the same purpose as the "MainWindow.xib" window that was present in versions of Xcode prior to Xcode 4. Both are essentially holding areas for all objects in the .xib. You can also drop the ViewController into the workspace and it will be added to the Dock (gutter). A ViewController cannot be added to a window. A ViewController's view can.

In Step #9, assuming you have created the class files and have selected the ViewController proxy in the MainWindow.xib, the class will be in the Custom Class drop down in the Identity inspector. The book (again working from the prior incarnation "Beg. iPad Development") may refer to finding it in the Attributes inspector.

Step #11. Apple is trying to compel you to use the accessor for the window, as you should, rather than directly calling the variable. (It is a private variable) If you note, they call it as follows

in the method that you add the subview. You should enter your method as
The list view is not available anymore. As I stated in a previous communication, there are two views; the default object view and the outline view.

If you haven't checked it out, you should read through the Xcode 4 transition guide, or possibly get a copy of Xcode 3.2.6 and try the projects in the earlier version as well as Xcode 4. The Xcode 4 quickstart guide should also be useful.

Bob

Bob: thanks always for your help.

Regarding Core Data, when I first attempted windowBasedApp, as per Chapter 4, build failed, with some complaint about "no available environment" or something like that. I Googled the error message and got many hits though not exactly my case. Of course, the initial windowBasedApp was simply declare it with Xcode and build it; fairly idiot proof, you would think. But it flat out wouldn't build [or run]. I checked Core Data, and it built and ran. Now I create the same project w/o Core Data checked, and it still builds and runs, so I cannot duplicate the original problem.

My step #4 problem was that all previous examples of dragging something from the object library [right pane] had as its destination the center iPhone display graphic. This time something different was necessary, i.e., dragging to the gutter/dock object. When you're starting from total ignorance, as I am, these minor differences become major differences.

As for step #11, the book on page 90 suggests:

[window addSubview:viewController.view]

but for reasons not clear to me, "window" does not exist, but "_window" does. This would appear to be a nuanced difference between Xcode 3.2.6 and Xcode 4.

Concerning _window, check out the @synthesize. You will see

This compels the use of the accessor, which is a good thing. You can still set the variable directly though the use of _window, but the implication is that direct assignment should be avoided. Proper and consistent use of accessors goes a long way in dealing with memory management and object-ownership issues. Getting accustomed to the conventions is a good thing, since many of the benefits of Key-Value coding require that certain conventions be followed.

This is a new convention introduced in Xcode 4. You could rewrite the @synthesize to be
and code as the book does and it will work correctly.



Bob