Interface Builder 3.2: Outlets and Actions
In previous versions of Interface Builder, you used the identity inspector to add outlets and actions to a user interface element. Interface Builder 3.2 moved this functionality to the Library. If the Library window isn’t open, choose Tools > Library to open it. Click the Classes tab in the Library window. Select a class. Use the Outlets and Actions tabs to view, add, and remove outlets and actions for the selected class.
Xcode 3.2: Project Templates Removed
In Xcode 3.2 Apple removed all Carbon project templates as well as the Cocoa projects that used Python and Ruby. You can install Xcode 3.1 alongside 3.2 if you need the templates Apple removed. Apple doesn’t officially support Xcode 3.1 on Snow Leopard, but Xcode 3.1 can be installed and run on Snow Leopard. If Xcode 3.1 doesn’t work well for you, you can copy the project templates to the user templates location so you can use them in Xcode 3.2. Refer to this blog post from the old blog for more information on where the templates should be copied.
The PyObjC and Ruby Cocoa websites are the places to visit for the latest Python and Ruby project templates. For those of you interested in writing Cocoa applications in Ruby, Mac Ruby is another project to check out.
Xcode 3.2: Creating Java Projects
In Xcode 3.2 when you choose File > New Project, there are no Java templates in the New Project Assistant. To create Java projects you must open the organizer by choosing Window > Organizer. At the bottom of the Organizer, you will see three buttons.
Click the + button on the left and choose New From Template > Java Templates to create a Java project. Click the right button at the bottom of the Organizer to show the editor. Use the editor to write your code.
Xcode 3.2: Changing the Organization Name
In Xcode 3.2 Apple made it easier to change the organization name so the copyright notice at the top of newly created files doesn’t say __MyCompanyName__. Choose Project > Edit Project Settings and click the General tab in the inspector. At the bottom of the inspector is a text field to enter the organization name. This name will appear in the copyright notice for any new files you create for this project.
Xcode 3.2: Where Did the Build Transcript Go?
The build transcript lets you see the details of how Xcode built your project. If you upgraded to Xcode 3.2 and looked at the build results window, you noticed the group of four buttons that let you open the build transcript was missing. How do you access the build transcript?
In the build results window you should see a listing for each step in the build. At a minimum, you shoud see one listing for each source code file in your project. Selecting a listing displays the build transcript button on the right side of the window. In the screenshot below, you can see the build transcript button next to the icon saying the file GameApp.cpp has 6 warnings.
Click the button to see the build transcript.
If a step in the build process generates errors or warnings, the build transcript button appears automatically.