Mac OS X Programming phần 9 pptx

Book: Mac® OS X Programming Section: Chapter 10. Bundles and Icons Registering a Creator Code Every file has a four-character type. The value, unsurprisingly, specifies the type of the file. An application always has a type of APPL. (Other common file types are TEXT for a text file and PICT for a picture file.) Every file can also have a four-character creator code, which is a unique value belonging to one and only one application. In the case of an application file, the creator code is an identifier of the application itself. In the case of a file created by an application, the creator code identifies the file as belonging to (or created by) the application with the same creator code. As an example of a creator code, consider Apple's SimpleText text editor application. The resource editor ResEdit can be used to ascertain the type and creator code of any file. At the top of Figure 10.6, you see that ResEdit reports that for SimpleText, the file type is APPL (it's an application) and the creator code is ttxt (a unique four-character value registered to this one application). Figure 10.6. The file type and creator of the SimpleText application (top) and of a file created by the SimpleText application (bottom). Now consider a file created by SimpleText. I launched SimpleText and created a new file, which I named ReadMe.txt. After closing that file, I viewed it in ResEdit. The results are shown at the bottom of Figure 10.6. In that figure, you see that a file created by SimpleText has a type of TEXT (it's a text file) and a creator code of ttxt (it was created by the application with this same creator code- SimpleText). An application's creator code is used by the Finder to associate files created by that application to that application. This system makes it possible for a double-click on a file to result in the launching of the creating application and the opening of the clicked-on file. Registering a Creator Code With Apple At Apple's developer site (http://developer.apple.com), you'll find a link to a technical support area (http://developer.apple.com/products/techsupport/) that includes links to pages that offer information about specific programming topics. The Registrations link takes you to a page (http: //developer.apple.com/dev/cftype) that includes information about registering a creator code (or application signature) for your own application. Click the Find link to move to a page that lets you enter one or more creator codes and then search to see which are available. In Chapter 5, I mentioned that I had registered a creator code for one of this book's example programs. Figure 10.7 shows the result of my search to see whether the creator code SPRB was available. It was, so the next step was to register the code with Apple. Clicking the Register new creator/file types link (see Figure 10.7) is how the registration is done. Figure 10.7. Searching at Apple's site for the availability of a creator code. The registration is short and simple. You enter a little information, such as your name and mailing address, and then you click the Submit button. That's it. If the creator code availability search told you that your code of interest was available, you now can consider it yours. Absolute confirmation is supplied in a couple of days. That's about how long it takes to receive a confirmation email notice from Apple. Assigning a Creator Code to Your Program After you've found an unused creator code and registered it with Apple, you can assign that creator code to your application. That's done from within Project Builder. Open the project that's used to build your application and click the Targets tab in the column of tabs in the project window. Click the target in the Targets area (the SuperBeepIcon target is selected in Figure 10.8), and then click the Application Settings tab from the row of tabs. As shown in Figure 10.8, you then can set the application's signature. Just type it into the Signature field. In this figure, you can see that I'm using the SPRB creator code that I've registered with Apple. Leave the Type field set to APPL. It stands for application, which is the type of file you're creating. With the signature set in the project, each build you perform results in an application with the specified signature. Book: Mac® OS X Programming Section: Chapter 10. Bundles and Icons Application Icons From the desktop, every application is displayed as an icon. Each real, shipping application has its own unique icon, one that displays an image that might provide a hint about the nature of the application. For instance, the TextEdit text editor application that is bundled with Mac OS X has an icon that looks like a piece of paper with writing on it and with a pen laid across it. When you build an application in Project Builder, that application is given a generic icon. By now, you should be familiar with this application default icon, but if you need to take a look at it, look at the icon for the BasicShapes program on the far left side of Figure 10.9. Although every application needs an icon, you probably won't want to go through the work of creating a unique icon for your short test programs. Thus, this Project Builder-supplied icon turns out to be a handy solution. When the time comes to build a "real" version of your program, though, you'll want to associate a "real" icon with that program. In this section, you see how to do that. Figure 10.9. Application icons (top) and document icons (bottom). Application and Document Icons On the desktop, an icon represents a folder or a file. If the icon represents a file, it can be for an application or a document created by an application. Figure 10.9 shows icons for four applications and two types of documents. The four icons in the top row of Figure 10.9 are application icons, while the two icons in the lower row are document icons. The leftmost icon in the top row of Figure 10.9 is the generic icon assigned to any program that doesn't explicitly define its own icon. Looking back at this book's examples reveals that every example project builds an application that sports this icon. The next two icons in the top row of the figure are the icons for real programs. TextEdit is Apple's text editor that comes bundled with Mac OS X, while Internet Explorer is, of course, Microsoft's web browser program. The last icon in the top row is the icon I've created for one of this chapter's example programs. In the bottom row, the leftmost icon is the one TextEdit assigns to its documents, while the rightmost icon is the one Internet Explorer assigns to its Hypertext Markup Language (HTML) documents. Apple recommends that every application have a custom icon that provides some visual clue as to the purpose of the program. The icon for Apple's TextEdit application conforms to that guideline. The icon for Microsoft's Internet Explorer doesn't (at least I can't make out much of a correlation between a lowercase e and a program used to browse the World Wide Web [WWW]). You'll find that numerous applications don't abide by Apple's guideline. Rather than provide feedback on the nature of the program, an application's icon might instead include some image that's already firmly set in the public eye. It also might be some version or adaptation of the software company's name or logo. In that spirit of rebellion, the icon I've created for this chapter's SuperBeepIcon program (shown at the far right of Figure 10.9) has nothing to do with sound or beeping. Note Other reasons that I chose to use a digitized image from my camcorder as the basis for an application icon include the fact that I don't have anywhere near the level of artistic skills necessary to create an interesting, professional- looking icon, and because I'm too cheap to pay a graphic designer to do the work of designing such an icon! The following three sections discuss the steps you'll perform to assign an icon to an application. In short, those steps are as follows: 1. Create an image in a graphics program and save it as a .pict or .tiff file. 2. Convert that graphic file to an icon file. 3. Include the icon file in a Project Builder project. 4. Within Project Builder, specify that this icon file be associated with the application that results from performing a build. Creating an Image for an Icon New to Mac OS X is the 128x128 pixel icon size. This very large pixel size means an icon can be designed with a lot of detail and look much better than ever before. Also new to Mac OS X is powerful scaling technology that enables a large icon to be accurately scaled down. Typically, you'll create a large 128x128 pixel icon and leave it to the system to scale it to the size the user prefers for the display of desktop icons. However, if you find that your large icon loses important detail in scaling, you can design intermediate-sized icons that assist the system in scaling. Those other sizes are 64x64 pixels, 32x32 pixels, and 16x16 pixels. In this chapter, I'll create just one icon-the 128x128 pixel size- and leave it to the system to handle all icon scaling. In the design of an icon you (or, more likely, a graphic designer) can use any graphics program that provides the desired results. If you're using a digitized image, you can use a graphics program to simply crop the image to isolate the portion of interest and then scale that image to 128x128 pixels. If your image is to be designed from scratch or if it is to be an collage or adaptation of clip art, you'll use graphics programs such as Adobe Photoshop, Adobe LiveMotion, and so forth. When you have an image with which you're satisfied, save it in a file of type .pict or .tiff. For this chapter's SuperBeepIcon example program, I saved some output from my camcorder to my iMac and copied one frame to the Clipboard. I then launched a graphics program (the shareware program GraphicConverter, which is discussed in Chapter 2, "Overview of Mac OS X Programming"), created a new, empty document 128x128 pixels in size, and pasted that image into the document. I dragged the pasted image around until the portion of the image of interest was centered in the document, and then I saved the document as a .pict file. That gave me a 128x128 pixel image, but it didn't give me a 128x128 pixel icon.There's one more program to run to accomplish that conversion. Saving an Image as an Icon After you create an image that's to be used as an icon, you need to import that image into the Icon Composer application. Icon Composer is another free development application from Apple. You'll find it in the Applications folder inside the Developer folder on your Macintosh. With your image created and saved as a 128x128 pixel .pict or .tiff file, launch Icon Composer. Choose Import Image from the File menu. As shown in Figure 10.10, the window that appears enables you to move to the folder that holds the image that's to be converted to an icon. Move to that folder now. Choose Thumbnail 32bit data from the Import To pop-up menu located at the bottom of the window, and then select the file of interest. Your actions tell Icon Composer that the file you're about to select holds an image that's to be used as a 128x128 pixel icon. Now double-click the name of the file that holds the image. Figure 10.10. Importing an image into Icon Composer. After you select a file, Icon Composer responds by placing that file's image into the Thumbnail box at the bottom of the icon window, as shown in Figure 10.11. Note that if it turns out that the file you saved as a 128x128 pixel image varies by even one pixel in either dimension, Icon Composer will ask you if you want the image scaled. Go ahead and let Icon Composer do this. The change won't be noticeable, unless your image is in fact of a size that varies quite a bit from the 128x128 pixel size of a thumbnail. Figure 10.11. The displaying of an imported image in Icon Composer. Now choose Save from the File menu. The file name can be of your choosing, but don't add an extension to the name. When you click the Save button, Icon Composer will add an extension of .icns to the name you entered. Save the file to the project folder. Adding the Icon File to Your Project Before the contents of a file can be used by a project, that file needs to be added to the project. In the Chapter 2 example of HelloWorldPict, you saw this was the case for including a picture in a program window. The same holds true for an icon. After using Icon Composer to convert an image to an icon and saving that icon to a file, you need to add the resulting file to a project. Open the Project Builder project that's to use the icon and click the Resources folder in the Groups & Files list in the project window (that selection determines where the added file will end up). Now choose Add Files from the Project menu. Select the .icns file to use and click the Open button. When prompted to specify which targets to add the file to, click the Add button. Figure 10.12 show how the SuperBeepIcon project (discussed ahead) looks after an Icon Composer file named SuperBeepIconApp.icns has been added to it. For organizational purposes, the icon file typically is kept in the Resources folder, although it doesn't have to be there for the icon to become associated with the application. If the icon file doesn't end up in the Resources folder, simply drag it there now. Figure 10.12. Adding an icon file to a project. Adding the .icns file to the project is one of two steps to getting a project to recognize the file's icon. Now you need to name the same file in the Application Settings of the project. Begin by clicking the Targets tab in the column of tabs in the project window. Click the target in the Targets area (the SuperBeepIcon target is selected in Figure 10.13). Click the Application Settings tab from the row of tabs. Now scroll down to the Icons section and type the name of the .icns file in the Icon file text box. In Figure 10.13, you see that the file name matches the name of the .icns file added to the project back in Figure 10.12. Figure 10.13. Associating an icon file with an application in a project. At this point, the icon in the .icns file will replace the generic icon that Project Builder uses when no icon is specified. Now when you build the application from this project, the resulting application will display the icon that's in the .icns file. Viewing the Results When you build an application from a project that includes a .icns file, that application displays the icon at the desktop. Unless you've specified otherwise in Project Builder, building an application from a Project Builder project places the executable in the build folder in the project folder, so you'll look in that folder to see the application. In Figure 10.14, you see the result of associating the icon shown in Figure 10.11 with the project shown in Figures 10.12 and 10.13. If your application isn't sporting the new icon, don't be alarmed. It might just mean that your desktop isn't updating promptly. If you built the application once without the new icon, the desktop might still associate the generic application icon with your program. Try this to remedy the situation: click the application icon in the build folder and copy the application to another folder. The duplicate application should now have the new icon. Figure 10.14. The newly added icon is displayed on the desktop. The size of the icon your program uses is adjustable by the user. Because you've created a large, detailed icon, the desktop is capable of accurately scaling that icon to a smaller size. To test this, you can copy the application from its folder directly to the desktop and then choose Preferences from the desktop menu. Drag the Icon Size slider control to different settings and watch the application icon (and all other icons on the desktop) change in size. Figure 10.15 shows desktop icons being increased to their largest size. Figure 10.15. Resizing icons (including your application's icon) on the desktop. [...]... turning your Mac OS 8 or Mac OS 9 code into an application that's launched in the Mac OS X space! Book: Mac OS X Programming Section: Chapter 11 Porting Mac OS 8 /9 Code to Mac OS X Carbon Dater: Getting Ready for Carbon You'll want to have a plan before jumping in and making changes to the code of your existing Mac OS 8 /9 application In particular, you'll want to know which Macintosh Toolbox routines... routines: http://developer.apple.com/techpubs/macosx/Carbon/ HumanInterfaceToolbox/IconServUtili/iconservicesandutilities.html Book: Mac OS X Programming Chapter 11 Porting Mac OS 8 /9 Code to Mac OS X IF YOU HAVE SOME MAC OS PROGRAMMING EXPERIENCE, you'll want your previous programming efforts to run on Mac OS X Fortunately, without any modification, most of your Mac applications will make the transition... native Mac OS X application, you need to port its code to Mac OS X Adding new Mac OS X features, such as support of the new Carbon Event Manager, to your program can take a fair amount of programming effort However, the benefits of Mac OS X make those efforts worthy of the time expended In addition, before you jump into a full-scale conversion, you can alter your older project's code to be Mac OS X compatible... environment of Mac OS X That is, when a user of one of your Mac OS 8 /9 applications copies that program to his or her Macintosh running Mac OS X and then launches that application, the program automatically runs under Mac OS 9 There will be no Aqua interface, no protected memory, and no other features that are integral to Mac OS X If you want users of your previously developed efforts to experience your... Book: Mac OS X Programming Section: Chapter 11 Porting Mac OS 8 /9 Code to Mac OS X Tips for Handling Major Porting Issues The larger and more complex your application, the more "gotchas" you'll encounter as you move the code from Mac OS 8 /9 to Mac OS X The following sections contain tips on dealing with those gotchas Start with PowerPC Code Macintosh computers initially made use of 68K processors These... http://developer.apple.com/macosx/carbon/dater.html q Carbon specification: http://developer.apple.com/techpubs/carbon/ q Mac OS X porting information: http://developer.apple.com/technotes/tn/tn2003 html q Universal Interfaces download: http://developer.apple.com/sdk/ q SDK download: http://developer.apple.com/macosx/carbon/index.html Book: Mac OS X Programming Appendix A Carbon API Summary AS YOU PROGRAM FOR MAC OS X, you... Chapter 9, "QuickTime Movies and File Handling," introduces Navigation Services and provides an example of its use in opening a QuickTime movie file Book: Mac OS X Programming Section: Chapter 11 Porting Mac OS 8 /9 Code to Mac OS X For More Information The following web sites offers more information on some of the topics presented in this chapter: q Carbon Dater download: http://developer.apple.com/macosx/carbon/dater.html... each Macintosh Toolbox routine that your application calls and compares each one to the Carbon API The result is that every function call is categorized as Supported API, Supported But Not Recommended, or Unsupported API If a call to a Macintosh Toolbox routine is supported, you know that this original Toolbox routine now exists in the Carbon API A good 70 percent of more of the Macintosh Toolbox functions... of this appendix loosely follow the order of appearance of the topics in this book For instance, you find Interface Builder functions, such as CreateNibReference, before QuickDraw functions, such as SetRect, because the Interface Builder material is introduced in Chapter 2, "Overview of Mac OS X Programming, " and QuickDraw is covered in Chapter 7, "QuickDraw Graphics." Book: Mac OS X Programming Section:... that you use the newer Carbon Event Manager routines in your Mac OS X application, but it's not a requirement The use of a couple other new technologies is required, though In addition, if your Mac OS X program opens or saves files, it must use Navigation Services routines in place of the original Standard File Package routines If your Mac OS X program enables printing, it needs to use Carbon Printing . turning your Mac OS 8 or Mac OS 9 code into an application that's launched in the Mac OS X space! Book: Mac OS X Programming Section: Chapter 11. Porting Mac OS 8 /9 Code to Mac OS X Carbon. http://developer.apple.com/techpubs/macosx/Carbon/ HumanInterfaceToolbox/IconServUtili/iconservicesandutilities.html Book: Mac OS X Programming Chapter 11. Porting Mac OS 8 /9 Code to Mac OS X IF YOU HAVE SOME MAC OS PROGRAMMING. they'll run only in the Classic environment of Mac OS X. That is, when a user of one of your Mac OS 8 /9 applications copies that program to his or her Macintosh running Mac OS X and then