Historical errata for iPhone SDK Development

I noticed a run-on sentence on page 9 in the Terminology callout box

from Jamie Phelps, Thx again!

In the text you call the new action “buttonPushed:” but in the referencing image Figure 2.2 the action is called “buttonClicked:”

From Brian Beers, Thx!

Change “create” to “created” in following sentence in first paragraph: “There are several other files create for us but we will look at many of them later….”

2.6 Configuring the View Controller

You forgot to say to connect the EditorVC to the file’s owner’s eVC outlet in IB

Cheers

2.5 Configuring the Text Field

you forgot to mention to @synthesize the *field prop in the implementation

Cheers

First full paragraph near the top.
“Each row of a contains …”
Should be “Each row of a table contains …”

Paragraph 1 of 3.2 … ‘To conform with the Modal-View-Controller …’.

Modal should be Model.

First of multiple occurrences of Xcode being called XCode. A bit petty but I guess that’s a privilege of being a beta reader! ;)

[…]just be the name of the cell’s class. In our case, since we’re not sub-
classing UITableViewCel, but[…]

It should be UITableViewCell

[…] sometimes you’ll want to group the list into discrete sections. A
row therefore in a UITableView is alway contained within […]

I think you meant always ;)

Paragraph 1, Line 1 : “Each row in a given section of a table view usually represented by …”

Should be: “Each row in a given section of a table view is usually represented by …”

Paragraph 2, Line 1 : “So say in this application we are eventually are listing teams …”

Should be: “So say in this application we are eventually listing teams …”

The book uses “XCode” in a number of places. The name is “Xcode” with only a capital “X” just like any other common name.

In the code snipped (StarterViewController.h) printed in the book, the line

@class EditorViewController;

is missing. The line is included in the download-code.

StarterViewController.h needs to #import “EditorViewController.h” or the build will fail.

The event is defined as buttonPushed: but then buttonClicked: is used on the following page

Paragraph 1 of 3.2 …“It defines methods that tell a table view know how to draw itself” should be “It defines methods that tell a table view how to draw itself”

On the left of that status bar you’ll see the number of cell bars available,
the name of your carrier, and an indication of whether you are using
edge, G3, or WiFi.

G3 should be 3G instead

In the code listing at the bottom of the page which carries over to page 48, you have included the line to remove the item from the teams array even though it is meant to be the boiler-plate code.

the array is not retained after allocation with arrayWithObjects. Better should be

self.teams = [[NSMutableArray arrayWithObjects: …] retain];

please remove my erratum for this page; I didn’t see the property assignment

Implementing the Browser
1st paragraph, last sentence:
… or when they hit “Return” no the pop-up keyboard.

should read
… or when they hit “Return” on the pop-up keyboard.

Cheers

Figure 9.2 “Rendering a web site with UIWebView”

is displayed right in the middle of a code sample, breaking it in two.

The sampple starts on page 125 and should be :

- (BOOL)textFieldShouldReturn:(UITextField *)textField {
if (textField == urlField) {
[textField resignFirstResponder];
[self loadURL];
}
return YES;
}

Cheers,
Florian

Page 132, the ‘Joe asks’ section breaks a code sample in two.
Code starts page 131 and ends page 133.

Cheers,
Florian

The code sample at the bottom of page 137 has line numbers in it, whereas the other ones don’t.

Cheers,
The nitpicker.

Second to last paragraph :

You can set the delgate for your animations

should read

You can set the delegate for your animations

Cheers,
The nitpicker.

I think you should explain in more detail how to connect the field’s delegate to the File’s owner. On first reading, I thought that implementing the two methods was connecting the delegate.

In the first full paragraph you tell the reader to set the File Owner’s navigationitem to reference the UINavigationItem. You cannot do this until you have done step 3.12 on page 54.

“Right between where we synthesized the teams instance variable and where the viewDidLoad method is…” In the code generated by the SDK (build 9M2517), there are already several methods between these two points.

“Our text view’s rows didn’t expand to fill the space provided…” This issue doesn’t appear with the SDK Build 9M2517, so the section is no longer relevant.

RootViewController.m should #import “AddTeamViewController.h”

In the first paragraph of section 2.4, “New->File” should be “Add->New File”.

> [tableView deleteRowsAtIndexPaths:[NSArray arrayWithObject:indexPath] withRowAnimation:YES];

“YES” must be “UITableViewRowAnimationFade” or something.

“This tells Inter face Builder that the ButtonViewController has a method called buttonPushed:.”

This should be buttonClicked instead of buttonPushed to go with the screenshots.

“when the text filed is done editing” should read “when the text field is done editing”

I found figure 1.9 (and accompanying explanation) for running your app on your iPhone to be a bit nebulous. While trying to follow your directions (and correlating THAT to what the Provisioning ‘How To’ on the iPhone Developer Program Portal was telling me) I kept getting an error in the installation of the Hello.app onto my phone. Having never set up a developer certificate before, I found it to be an interesting process. In the end, following the Provisioning ‘How To’>Building and Installing your Development Application… led me to use the ‘Build’ Tab on the ‘Info’ dialog of the Target Hello.app whereupon the app installed and ran properly.

actually the whole viewDidLoad method is commented so the enclosing /* and */ must also be deleted in addition to uncommenting the line inside the method.

The sentence that reads “Finally,you’ll move to Xcode to create …” needs a space after the comma.

In the last paragraph, after the line “Now we need to setup the File’s Owner to be the EditorViewController class.”, I would add “Select the File’s Owner object, open the identity inspector…”. If the object is not selected, or if a different object is selected, typing “Ed” in the Identity inspectors class field will not autocomplete and would be wrong.

“let’s walk through each code” should read “let’s walk through each line of code”

In section 2.3, at no point do you mention that the StarterViewController File’s Owners view should be connected to the View object. Failing to do this results in an error: ‘-[UIViewController loadView] loaded the “StarterViewController” nib but no view was set.’

This is really nitpicky…

You say “Your first run will be a simple white background (a great flashlight
app).”

When actually the default is a grey background. But I did enjoy the flashlight joke. :-)

In the second paragraph you tell the reader to open the HelloViewController.xib file. You then go on to refer to it as a nib file. For people completely new to IB, you might want to include a footnote or other explanatory text that talks about how a xib file is an XML equivalent of a nib file which is easier for version control systems to deal with. Also explain that the term “nib” originally refered to “NeXT Interface Builder” files and that the MAC OSX IB is derived the NeXT one. And if you really want to be long winded, explain that when the project is built, the xib files are used to generate nib files that are stored in the app bundle.

Just a suggestion.

In the last sentence on the previous page you say:

“The next step is to get our application to respond to the rotation of the device.”

Then in the first sentence of section 1.4 (which is the next one that a user would read) you say:

“Recall that we want the text to rotate when the device is rotated.”

Is our memory really that bad? :-)

In the first paragraph of section 1.5, 5th sentence, toward the end, you have “… with you iPhone developer certificates.” The word “you” should be “your”.

You assume that users have already signed up and gone through the (multi-hour) process of getting dev certificates, provisioning profiles, etc all setup when you say:

“however the identifier has to match one of the provisioning profiles you set up with you iPhone developer certificates”

IMHO this app store/development setup process should be given an overview, or at least explain what all the pieces do. I think a number of developers who have not worked with digital certs before may encounter a great deal of uncertainty in this process that is poorly documented by apple.

In any case, you should not assume the developer has gone through this process. Is it really required for getting through all the examples in the book? What if I want to read and test the waters without investing in the $99? Just a thought…

You state “Your inspector should look like Figure 2.2, on page 26.”

A few times now you have placed screenshots 2+ pages from the relevant content. Is it not possible to get the screenshots inline (wrapped) with the text?

No period at end of sentence:

…requires more than one view controller

“I promise the bumpy feeling won’t last
long soon you will build your intuition and all this jumping back and
forth will make sense (and you’ll even come to like the fluid nature of it,
promise).”

perhaps should be:

“I promise the bumpy feeling won’t last long and soon all of this jumping back and forth will become almost intuitive (and I promise you’ll even come to enjoy the fluid nature of it).”

At the very least you need an ‘and’ before the ‘soon’, which is currently missing.

“In this we are going to build another simple application that has two
view controllers.”

should be:

“In this next example we are going to build another simple application that has two view controllers.”

“two fold” should be “twofold”. See dictionary dot com

This errata application silently drops any submissions that have a URL link in them… I added a link to a dictionary app to substantiate my errata report for page 28. I never appeared and I had to submit again, guessing that the link was the issue. Can you please alert the submitter if there is prohibited content?

“first hand” should be “firsthand”

“So if you don’t already have Xcode fired up do
that now, then open the Starter.xcodeproj and then”

This is unlikely as you just had us create the project a few paragraphs earlier. I would remove this bit…

“Save your work in Xcode and go back to Inter face Builder and you’ll see the action and the two outlets that you just added.”

Actually, you will only see this when you go back to IB if you also first select the ‘File’s Owner’ object.

“Back in Interface Builder, Control click on the button and drag to the
File’s Owner object in the document window.”

Umm, you just told us to go back to IB in the previous sentence.

" The ’Return’ key is set to ’Done’ so the user knows
that when she is finished typing she can hit to say she is done."

Perhaps should be:

“The ’Return’ key is set to ’Done’ so the user knows that when she is finished typing she can simply touch it to finish.”

Major confusion point in the text in section 2.4 Configuring the Text Field. You discuss (for more than a page) how to set the text field attributes correctly, but nowhere in sections 2.2. or 2.3 have we put a text field in the view. You instead instructed us to insert a UILabel. It took me a few minutes of wondering why I could not see the inspector attributes for a textfield when looking at the label attributes. Perhaps this section needs to go after we create the modal dialog for entering text?

In the objective-c properties sidebar:

‘through’ should be ‘thorough’

Huh?

“This is because the only the the compiler”

This section really needs clarification:

“Select the new view controller and open the Attributes inspector (Command-
1). Set the nib file name to Editor and then set the class name to Edi-
torViewController in the Identity inspector. And the final step, connect
the editorViewController outlet to this new view controller. Control click
on the files owner and drag to the new view controller. When you release
choose editorViewController make the connection.”

Especially the connections from file’s owner. I was scratching my head for a couple of minutes trying to figure out what it was you were trying to get us to do.

In the description, “In the list of actions click the ’+’ button and call the action buttonPushed: (make sure to keep the colon).”

While in fact the action you are creating is called buttonClicked, and the diagrams show that also.

“That was a bit of work but we’re done with everyone we have to do to
add a new team to the list.”

Should be ‘everything’ I suppose.

“It is typical to retur n YES from this method but if you
wanted to do some validation and keep the text field from resigning first
responder status you can NO.” should read “…you can return NO.”

The version of Xcode I am using 3.1.1 with iPhone 2.1 has the tableview setup to auto-expand without the need to make these changes.

In the last paragraph of section 2.1 “Your First View Controller” the first line says:

“Now we need to tell IB about our intent with the view controller SO CAN connect the button to the view controller”

I believe its missing an “it”. It should say:

“Now we need to tell IB about our intent with the view controller so it can connect the button to the view controller”

The action of adding navigation item is not correct, your description:
—
Our AddTeamViewController views needs a title and a button to get back
to the list of teams. Search for “Navigation Item” in the Inter face Builder
library. Drag an instance into our AddTeamViewController Inspector win-
dow. Control click the File’s Owner to the “Navigation Item” and assign
it to the File’s Owner’s navigationItem outlet. Then set the title of the
Navigation Item to “Add Team” in the attribute inspector.
—
But you don’t jet assign file’s owner to AddTeamViewController, so it can’t have outlet.

In Section 2.1, when we add the “buttonClicked” action to our View Controller, in the book you say that we should go back to Xcode and write the following method declaration:

- (void)buttonClicked:(id)sender;

That, I believe, is incorrect. Since its linked to a user interface element it should be an IBAction and not void, as follows:

- (IBAction)buttonClicked:(id)sender;

Cheers.

“turn on spring’s for both directions” - should be “springs”.

(Incidentally, when copying/pasting the text from Preview, there was a space between the ‘r’ and ‘n’ in “turn”. Might reflect a bug in formatting.)

“resized or when it’s super view is resized” (its)

“unwritten chp.views for now though”

Needs semi-colon after “chp.views”

“We are now finished with updating the UI.” This should be the start of a new paragraph; it doesn’t really belong with the previous sentences. Better yet, drop it and the next sentence entirely.

(Also another “it’s” on that page)

“If its easier to find what you are looking for you can
hold down the alt key”

Suggest specifying it as the “option” key instead, since that’s how most Mac users think of the key.

In the last paragraph of this page there is a parenthesis that reads:

“(I warned you it would be be a bit bumpy)”.

There only needs to be one “be”.

“Build & and Go”
“with you iPhone”

“Here is the code this application.”

“In Xcode open the ButtonViewController.h file and add a declara-
tion for the buttonClicked: method.”
You should add information where to put the declaration (after interface ... {} and before end).

Missing period after first sentence in the “2.2 Multiple View Controllers” section.

2.4 Configuring the Text Field - WHAT text field? We were never told to put one on. This whole chapter seems like it was written by someone else and it’s much harder to follow.

In the first Paragraph is says " and choose New -> File from “, it should be ” and choose Add -> New File … from ".

In the last paragraph when opening the Identity Inspector you need to have the File’s Owner Object selected. By default this is not selected so you may want to state it here since this is still probably a new concept to people.

The last sentence on this page says “Control click on File’s Owner and drag to the View object connect the view outlet (view is inherited from UIViewController and must be connected).”
This reads funny to me. I suggest “Control click on File’s Owner and drag it to the View object to connect to the view outlet (view is inherited from UIViewController and must be connected).”

In the second paragraph it says “To fix that add an import near the top of the file for the EditorViewController.h header.” It’s not clear what file needs to be edited. I suggest saying “To fix that add an import near the top of the StarterViewController.m file for the EditorViewController.h header.”

needed an #import “AddteamViewController.h” in RootViewController.m

The fourth paragraph says “Before we do, let’s walk through each code to understand what it’s doing.”
I believe this should be “Before we do, let’s walk through each line of code to understand what it’s doing.”

Paragraph one ends with “being used for performance.” I think this should be “being reused for performance.”

The second sentence of paragraph 2 says “Each cell has an image of the team’s logo on the left and the teams name as the text in the middle.” The second “teams” is missing an apostrophe. So it should be like this “Each cell has an image of the team’s logo on the left and the team’s name as the text in the middle.”

The last paragraph says “…in RootViewController.
The default implemtentation returns YES…”. This is not true. Here is the default implementation from my project:

- (BOOL)shouldAutorotateToInterfaceOrientation:(UIInterfaceOrientation)interfaceOrientation {
// Return YES for supported orientations
return (interfaceOrientation == UIInterfaceOrientationPortrait);
}

The viewDidLoad method in my project does not look like what is shown. Here is what I saw:
/*
- (void)viewDidLoad {
[super viewDidLoad];
// Uncomment the following line to add the Edit button to the navigation bar.
// self.navigationItem.rightBarButtonItem = self.editButtonItem;
}
*/

In the second to last paragraph when creating the new view you need to make sure Cocoa Touch is selected in the nav on the left of the Choose a Template Wizard. If you have Cocoa selected there is a view option as well.

Ok, this chapter is just a mess guys. The first chapter was very well done but here in chapter 2 it’s all confusing and I don’t feel like I have a grasp of why we did what we did to make the example work. I feel like I was able to build the Starter application only because I followed the steps (even with all the errors) and not because I was understanding the concepts. This chapter needs a lot of work.

In 8.2 it says to add the lib-sqlite3.dylib it’s already added for the sample code.

I don’t think “niggly” is a real word, is it? (line 3)

“Right between where we synthesized the teams instance variable and
where the viewDidLoad method is, add this initialization code:”

This instruction does not truly fit with reality (at least for the latest versions of XCode. Between the teams instance variable and the viewDidLoad method are several pre-generated methods. And viewDidLoad is also commented out. In my generated code it would be more accurate to say:

“Right between where we synthesized the teams instance variable and
where the numberOfSectionsInTableView method is, add this initialization code:”

In general though, I think you would be better served in this case, as well as throughout the book to actually provide a few lines of context around any code that you are providing. This will eliminate confusion, and will require less reader parsing of text when the code sample is self documenting as to the change. You may even highlight the new code in a bold font and the context code in a lighter color.

Before starting in with Section 4.7 you also need to add:
#import “PlayersTableViewController.h”
to the top of RootViewController.m

“Before we do, let’s walk through each code to understand what it’s doing.”

I suspect you meant ‘each line of code’. Or perhaps ‘each part of the code’?

[teams removeObjectAtIndex:indexPath.row] gives me a warning: “NSMutableArray” may not respond to “-removeObjectAtIndex:” (Messages without a matching method signature will be assumed to return ‘id’ and accept ‘…’ as arguments".

And when I run the app and try to delete the row, it freezes once I press the red “Delete” button on the row I want to delete.

The end of the second paragraph of the Using a ready-made button section says “… list of basketball teams in the (as yet) unwritten sec.deletingRows.” That section exists now so you may want to update this.

It would appear with SDK 2.1, the default for the table view in the Navigation template is to expand with the view, so these steps are no longer necessary.

It might be helpful here to mention that setting the delegate and the return button for the keyboard can be done in IB.

Move figure 4.2 after the start of section 4.7. It seems out of place at the end of section 4.6.

After clicking on “Download HelloiPhone/Hello/Classes/HelloViewController.m”, the browser doesn’t show the file contents properly, as though the web server doesn’t know how to display the file as code or whatever.

Header file for StartViewController.h should include

#import “EditorViewController.h”

.Otherwise, you will get 6 build errors, because the editorViewController constant cannot be referenced.

I’m quite new to Cocoa but one of the first thing I learned was that if you did an alloc you have to do a release. In the method loadFileContentsIntoTextView you are doing an alloc both on inputStream and readBufferString without a release.

Be nice to download a .dmg file that has the entire project in it, so we could compile it and run it - and maybe compare to our own (that isn’t working).

3rd line in paragraph for section 3.9, “edit mode and then make the UITableViewdataSourcerableView:commitEditingStyle:forRowAtIndexPath:” should be wrapping in there somewhere - it extends past the margin of the text column.

Typo/Error on the call of the animation values.
animation.values = [NSArray arrayWithObjects:initial,
intermediate, final, nil];

should be changed in all code (example in book and supplement):
animation.values = [NSArray arrayWithObjects:initial,
middle, final, nil];

All considering that you just gave a NSValue to *middle in the page prior.

In Xcode select FileNew File… (or Command N ). When propmted choose
a UIViewController subclass that we’re going to call AddTeamViewCon-
troller.

Note “propmted” should be “prompted”.

Include the code for dealloc method, as well as the synthesize (boring, but helpful). Do the same thing on page 61 too (include the code).

Make Figure 3.13 description be “Figure 3.13: Confirming outlets are set correctly (Right Click on File’s Owner)”

If the title property set in the code sample at the top of the page is defined as the rest of the properties discussed so far: property (nonatomic, retain) NSString *title;
then this sample will leak. Either an assign property, autoreleasing the string or explaining that memory management is ignored here would fix that.

Re: being “welcome to try” to compete with Safari - given the apparent stance of Apple on this, this may not be that appropriate to suggest.

Yor write:
Right between where we synthesized the teams instance variable and
where the viewDidLoad method is, add this initialization code:

But in XCode, viewDidLoad is long way down in the code. So just change it to read:
Right after where we synthesized the variable…

Re: #34812
Same here. Default is bound to all 4 edges. 3.1 + 2.1

Default in XCode 3.1 / iPhone 2.1 is
self.navigationItem.rightBarButtonItem = self.editButtonItem;
Edit in the left is old style. Also, now many default functions in the template code is commented out with block comments /* … */

Like most databases, works with SQL, Structured Query Language,
a widely-supported standard for expressing database commands as
human-readable, dynamically-composable command strings.

Seems like an SQLite is missing in the sentence above.

In the ‘Objective-C Properties’ box, you very briefly describe the property and synthesize compiler directives.
I feel these should really have a little more explanation.

Either way, for your external references, the apple docs has a simple explanation in the ‘Learning Objective-C: A Primer’, ‘Properties’ section.

and a full breakdown in the ‘The Objective-C 2.0 Programming Language’ doc, ‘Declared Properties’ chapter
(not sure if I’m allowed to post direct links to apple docs here?)

The sample code block on this page, and its fuller implementation on the next page are poorly presented.

"
- (UITableViewCell )tableView:(UITableView)tableView
cellForRowAtIndexPath:(NSIndexPath *)indexPath {
static NSString *MyIdentifier = @“Team”;
"

It is not made clear that we are not to add this as a new method, but instead should be modifying a single line of an existing method.

Additionally, you suggest calling the cell identifier by the name ‘MyIdentifier’ when the default generated method uses ‘*CellIdentifier’.

Also, you do not setup MyIdentifier to be a pointer as the generated code does.

Then on the next page you give the full implementation of the method. I would suggest instead collapsing these into a single code sample, and stay as close to the system generated method as possible and highlight only those lines of code that are different than the default code.

The sample code block on this page, and its fuller implementation on the next page are poorly presented.

It is not made clear that we are not to add this as a new method, but instead should be modifying a single line of an existing method.

Additionally, you suggest calling the cell identifier by the name ‘MyIdentifier’ when the default generated method uses ‘*CellIdentifier’.

Also, you do not setup MyIdentifier to be a pointer as the generated code does.

Then on the next page you give the full implementation of the method. I would suggest instead collapsing these into a single code sample, and stay as close to the system generated method as possible and highlight only those lines of code that are different than the default code.

(AND AGAIN I had to use my back button to save this post since your system seems to have silently ignored it since I originally copied in some of the sample code… How can we effectively use this reporting system if neither hyperlinks (to a pastie) nor code samples seem to be allowed?)

(Dave says: I disable posts with hyperlinks because we see a LOT of spam attempts. The alternative would be to require to to log in to post)

implemtentation should be ‘implementation’

verticle should be vertical

Echoing the first comment since it seemed to miss the last rebuild of the book. The buttonClicked: method only worked for me when I changed the expected result type from void to IBAction.

First sentence, second paragraph of 11.4 has a typo in it. “Surfface” —> “Surface”.

You state:

“Save the nib and let’s Build & Go again. Now if we rotate the device it
does what we want. Go ahead and rotate it a full 360 degrees. It should
behave how we expect in all cases.”

I think that most users will be doing a ‘build & go’ with the simulator as the target and not running this bit of test code on actual hardware. There is no way (at least as far as I can tell) to turn the simulator 360 degrees and ever get to the upsidedown portrait view. I can only get it into standard portrait and left horizontal positions.

Personally I would not have added the ‘(surprise, surprise)’ as it implies that everything that has preceded has been really easy.

I would additionally comment that so far in the book I have been getting good at copying and pasting code, but I don’t feel you have been really teaching me much to understand what the code I am copying really means, and how I would go about knowing how to implement it when I am creating my own app.

See Hillegass’ Cocoa Programming for OS X for a much more instructional style. I heard the authors in a recent podcast episode saying that they were targetting people who are experience developers, but not experienced with cocoa/obj-c/cocoa touch. It actually feels so far like they are really targeting existing mac developers, who just want to expand into iPhone dev as well. My $0.02. :-)

By using example, code doesn’t work as expected.
In ordre it works, i add in textFieldShouldReturn method of EditorViewController class :
field = textField;

If not, the Label text doesn’t change even if edited.

Maybe, it isn’t the “coorect” solution, but i think there is a mistake.

The overall book is great, but I think there needs to be a short primer on Cocoa in general. Since I only know the very basics of Cocoa, I did get a little lost.

“You might have noticed that the value retur ned by NSHomeDirector y( )
function is an NSString, not some sort of “NSFile” class. That’s because
in Cocoa, files are always paths represented as strings."
or NSURLs with the file:// scheme.

Whoah…. What a mess. You start dropping terms like UIKit object and nib file, without ever explaining what they are. Luckily, I happen to know what these things are, but I don’t know them from your book.

“Once saved, go set File’s Owner to be PlayersTableViewController.” - being a beginner, I have no idea how to do that, so I imagine you’re asking me to check some text previously - be nice to let me know where I can read about it (again - because I forgot).

Same goes for “Assign that table view to be File’s Owner’s view outlet.” - yep, no idea…

In the first paragraph: “When the device rotates the label’s superview…” should have a comma - “When the device rotates, the label’s superview…”

Second paragraph, second sentence. “its” should be “it’s”

“Control-click the Navigation Item. Notice the three button related outlets: backButtonItem, leftButtonItem and rightButtonItem.” at the bottom of the page is missing the “Bar” bit out of the outlets - should be:
backBarButtonItem, leftBarButtonItem and rightBarButtonItem

It would seem for the File System Explorer App, it’s assumed the reader will just follow along with the sample code. This is a departure from previous chapters that were very specific about the steps necessary with Xcode and Interface Builder. It would be nice to have those steps laid out ( like what type of project to start, etc) or to have a more explicit note about wanting the user to follow along from the sample code.

Just after adding the code from the begining of 2.5 Creating the View Controller, I have two errors that at the end of the chpater, still there and of course can’t run the Starter Project. This is my third try so maybe is something wrong someplace. The errors are in the EditorViewController.m. There are also two warnings but they are normal in this stage of the project.

I don’t know if I missed it but I don’t know where we can dowlonad the full project in case something is wrong, to double-check that the code from the book is ok.

I tried to download some of the files and I see some differences between the code created by default by XCode and the code that appears in your files, for example:

// Override initWithNibName:bundle: to load the view using a nib file then perform additional customization that is not appropriate for viewDidLoad.
- (id)initWithNibName:(NSString )nibNameOrNil bundle:(NSBundle)nibBundleOrNil {
if (self = [super initWithNibName:nibNameOrNil bundle:nibBundleOrNil]) {
// Custom initialization
}
return self;
}
*/

that in some of your files appears uncomented and I can’t see any reference on your pdf/book,

and that’s all, thanks for giving us the oportunity to have such book in the initial state before they are ended and printed, thanks a lot !

regards,

r.

code snippet: if you do not add #import “EditorViewController.h” into StartViewController.h just after #import <UIKit/UIKit.h> you will get error because it says that EditorViewController is undeclared.

“And then make the connection in IB from the File’s Owner to the text field in the user interface”
I’m working on IB with Editor.xib: if I control-click on “File’s Owner” and drag on the text field it prompt me to choose “field” or \t “view”… what should I choose?

after building my application, when I click on edit, an empty window shows up instead f the edit window…. what did I do wrong?

it would be good to include a quick troubleshooting guide when something does not compile or it compile but it does not work as expected.

I became completely confused when I hit section 2.4 Configuring The Text Field because up to that point there was no mention of any text field, nor had we created one yet. It took me some time to figure out that 2.4 was a general discussion and that the exercise continued in section 2.5 - several pages later.
Please re-work this transition.

Last sentence of first paragraph should read “You just have to add your custom…”

I did not find anywhere in this chapter were you instruct the user to synthesize EditorViewController and set its property

I found the code only when reviewing your code samples. It won’t work without this.

I am enjoying working my way through your book and glad to have it!

The first full paragraph, which attempts to set up the navigationItem, doesn’t work at all. Perhaps the instructions are unclear and I messed up the demo, but when I drop off the Navigation Item into the AddTeamViewController window (which contains File’s Owner, First Responder, etc.) I am unable to control click the File’s Owner to the navigationItem of the Navigation Item because nothing pops up when I release the control+click while I’m hovering over the Navigation Item. Help would be greatly appreciated here.

The book suggest that the Utility template is being used to generate the FlippingPreferableClock application. However, the example program has three views and a single controller, which certainly is not generated by using the Utility template, as such an app has three controllers. I think it would be better to either use the Utility template, or to explain more clearly how one can add a settings view to an existing app.

“They are also really good at letting you drill down into heirarchies of data.”

‘i’ before ‘e’, except after ‘c’ ;)

While it’s great to have ANY book on the SDK at this time, may I suggest that you give your PDF a good spelling and grammar check even at this point. Nearly every page has irritating errors.

it would be a good idea to point out right in the introduction that the sample code is available on the website and that it is most helpful if people access it when trying to overcome roadblocks.

Looking forward to all the chapters ahead and the final masterpiece!

Grandpa Brian - publisher of apps for serious hockey folks.

Additionally, “hieirarchy” should be spelled “hierarchy” and “heirarchical” should be spelled “hierarchical”.

Is it just me or does the word hierarchical look stranger and stranger the more you look at it?

Last line of page - “palatte” should be “palette”

I think this chapter could use a simulator screenshot of the add team view showing the text field and the navigator item.

In the second paragraph of page 39 there is a sentence that reads:

“This is because the only the the
compiler knows about this point is the forward declaration we placed
in the header”

That makes no sense whatsoever. Hopefully it gets fixed.

In the code listing for the buttonClicked: method, the line that currently reads:

center.y +- 100.0f;

should read instead:

center.y += 100.0f;

Your coverage of tables is, frankly, really weak. This is one of the key features of this platform and needs substantial focus. I would like to at least see the addition of table indexes along the right-hand side of the screen and doing anything more than displaying a simple text line in a cell.

Thanks for considering. Elia

“Though you could set any object to serve as a table view’s data source, you’ll almost always have your UITableViewController play this roll”

roll => role

“With the delcartion added” should probably read “With the declaration added” in the second-to-last paragraph.

Second paragraph of 3.11 should be .xib instead of .nib (two times here). This isn’t the only occurance in the book, just as an example here.

commuincation -> communication (last line of the page)

In last sentence of first paragraph,
“You just have add your custom implementations to pre-existing methods for the features you are interested in using.”

Should read "You just have to add your custom implementations to pre-existing
methods for the features you are interested in using.

Last 3 bullet points say “File’s Onwer” instead of “Owner”. 4th bullet on next page is correct.

Inconsistent in using “OpenGL” vs “Open GL” (with a space). I believe the accepted standard is OpenGL without spacing, even when used with ES as in “OpenGL ES”, though it may be worth confirming. Regardless, you alternate between the two frequently and at the very least should choose one and be consistent.

‘CALayer’s are order on two properties’
should read
‘CALayer’s are ordered on two properties’

first sentence contains ‘effects’ - this should be changed to ‘affects’.

General comment about section 11.3 - you need to provide a little more background - flesh out what you mean by ‘other detailed operations’ with an example.

I really think that having an example with a more complex example (eg, have some layers move along a predefined path, eg sine wave) would be a good idea.

Incomplete sentence, Paragraph 3, Sentence 3. “Allowing the second object to be written independently from the
first.” This clause should probably be tied to the preceding sentence with a comma, not a period. Or perhaps start the sentence: “This allows the second object to be…”

Its and It’s are misused throughout the text, although not consistently. Some samples: p19,p20(twice) “its” is used where “it’s” is needed for “it is” in three successive paragraphs. Then both “its” and “it’s” are used correctly in the next paragraph (beginning with “Once it’s launched”. And “it’s” is mistakenly used as a possessive instead of a contraction, such as on p16 and p17 where the term “it’s superview” is mistakenly applied.

Hi,
I think this chapter should also show how to detect swipes such as left or right.

It seems that the book took a drastic turn at this point. Previously, I was able to follow along in the book and build the sample applications as I read the chapter. Now, it seems like we’ve shifted to a “download the sample code and follow along”. I like the first approach much better.

A chapter on testing would be useful.

The .nib files in the second paragraph are .xib files.

the last paragraph of page 47 (Beta 3.0) says:

“Before
we do, let’s walk through each code to understand what it’s doing. ”

I think it should read:

“let’s walk through each LINE OF code to understand what it’s doing.”

Exchange first and last paragraphs then the AddTeamViewControler nib file will work.

propmted ==> prompted

“Control click the File’s Owner to the “Navigation Item” and assign
it to the File’s Owner’s navigationItem outlet." ==> I don’t think this action can be done yet because we haven’t created the AddTeamViewController yet.

everyone ==> everything

I’m fairly new to SQLite, so forgive me if I’m wrong here… but might you be better off calling sqlite3_prepare_v2 with –1 as the third parameter, to let it determine the string length? While something like this might be done for a performance advantage (probably small, since developers will likely cache the prepared statement), the SQLite documentation says that the third parameter should be the length in bytes, including the terminating null. The example on the top of page 134 would seem to have two problems, then: first, the count doesn’t passed to sqlite3_prepare_v2 doesn’t include the null terminator; and second, the count being passed is the number of Unicode characters in insertStatementNS, not the number of bytes in the UTF-8 string (if there are any wide characters in the UTF-8 string, the number of bytes will be greater than the number of characters).

If I’m way off here, I’d appreciate it if you could set me straight: dave@ruske.com.

Thanks —- and by the way, great book!

In chapter 5.2, the first and second paragraph say almost the same thing.

[First paragraph]
“In a real world application you’d build out a set
of model classes to represent your data and then store that data in a
database or file (I prefer a database). For this simple example though
we will just use NSDictionary objects to hold the data.”

[Second paragraph]
“The first thing we need to do for our example is to create the data. In
real world applications you would develop a set of model classes that
would contain the data and then persist their infor mation into either a
database or file. In our case we are going to keep it simple and just use
NSDictionary and hard code the data.”

The first two of the bottom three bullets that explain connection of the Outlets to the views should read the other way round: “Connect File’s Owner to the text field” and “Connect File’s Owner to the UIView”
If you try connecting the other way round, the suggested outlets don’t show up and you can’t connect.

3.2 - Feeding data to a table view

Third paragraph, first sentence:

“…play this roll.”

Should read:

“…play this role.”

4th sentence “NSIndexPaths we us NSArray’s” should be “use’ not ”us"

In the first complete sentence of the page under figure 2.5 you say:

“Select the Files’ Owner object and you’ll see the action and the two outlets that you just added.”

You don’t mention anywhere where you are supposed to look for the outlets and actions. I suggest that you might want to mention that you will find these recent additions in the identity inspector (cmd+4) for the File’s Owner object.

“In the wizard that pops-up choose the UIViewController subclass item in the iPhone OS -> Cocoa Touch group.”

The group is actually called “Cocoa Touch Classes”.

“Select the new view controller and open the Attributes inspector (Command-1). Set the nib file name to Editor and then set the class name to EditorViewController.”

This implies that the nib file name and class name are on the Attributes Tab when the classname is on the Identity tab (command-4).

The second sentence of the page reads “…and still get some much done…”. It should probably say “…and still get so much done…”.

The second sentence on the page reads “…you can look at just the icons, which is they way…” this should probably read “…you can look at just the icons, which is the way…”.

truncated sentence (maybe still being worked on?):
…“make just about any type of”

In the first paragraph there is a line that describes the first responder that reads “The first responder is the object that is first inline to get certain types of events..” and it should probably be “in line” rather than “inline”.

The second sentence in the last paragraph reads “You have just build…”, but it should probably say “You have just built…”.

In the first few sections of this chapter the term section was thrown around several times. I had already played around with UITableViews before and still found myself a bit confused on what a section was. I think this would be an appropriate place for the anatomy of the UITableView, i.e., for a picture of a UITableView with at least two or more sections and labels of what each piece of the UITableView is (e.g., section, row, parts of the UITableViewCell, etc.).

in the code, there’s a [self createData]; but no mention of why it’s there (on this page) - do I add that new line now, or…?

In the first sentence of the third paragraph you have the following phrase “…by providing us will an already implemented…”, but I believe that “will” should be “with”.

The query code that appears similiar to…

const unsigned char* itemValueC = sqlite3_column_text (dbps, 1);
NSString *itemValue = [[NSString alloc]
initWithCString:itemValueC encoding: NSUTF8StringEncoding];

and others of a similiar type produce an error. A simpler line for this which does not produce errors would be:

NSString value = [NSString stringWithUTF8String:(char)sqlite3_column_text(dbps, 2)];

To help explain the ‘Set the nib file name to Editor..’ section, a screenshot of the Attributes panel with the field shown would be helpful, or perhaps directly reference it as the ‘NIB Name’ field. I accidentally set the title field the first time, and had to retrace my steps to catch this one.
Could perhaps point out/show that in the ‘Editor View Controller’ window, it says ‘(Loaded from Editor.nib)’ to confirm the correct settings are in place.

We need to do two things ==> We need to connect two things

passing in. the ==> passing in the

[Note: I really want this book to succeed, so take this and all my future suggestions in the constructive way in which they are intended.] There’s no explanation of what a File Owner is: a “Joe Asks” would be really appreciated here.

We then push it onto the
navigation controller’s view controller stack. ==> May also want to mention after this line that an import statement is needed for AddTeamViewController.

It may be obvious to most, but when you say “Add the following code to addButtonWasPressed.” It might be good to point out its in RootViewController and not the current open file.

I also has to add #import “AddTeamViewController.h” to RootViewController.m before the code would compile.

Xcode 3.1.1 generates viewDidLoad with the edit button on the right of the bar, not the left.

“how to handle the reordoring of rows”
->reordoring

MyIdentifier is a variable, not a class, so shoud be myIdentifier and not MyIdentifier (should start with lower case letter)

… “UIKit developers prefer since its smaller and they
recognize the icons.”

should be:

“UIKit developers prefer since it’s smaller and they
recognize the icons.”

(mind the apostrophe in it’s)

In chapter 3 we do some pretty cool but complex stuff. We learn how to add and remove items form a table view.

Now, near the end we create a new nib file with the textField where we type our new entry’s name. We set up the AddTeamViewController as the delegate programatically, but couldn’t it have been done in Interface Builder as well?

From what I have seen there are several ways to do things in Xcode and Interface Builder.

We also set up the keyboard to show a “DONE” key instead of return, again I did that in Interface Builder.

I was just checking to see if both ways are ok, because sometimes I get confused as to what I can and cannot do within interface builder that must be done in code.

From Felipe Laso

in addition to #35040, since I’m bored tonight, a quick grep gives the following places where it’s should be its and vice versa:

Missing apostrophe:
18 “If its easier to find what you are looking for”
18 “100% accurate but for now its close enough”
20 “updated the UI and the code now its time to run,”
21 “Once its done compiling”
21 “Once its started try rotating the device”
25 “its the same file we started with”
29 “developers prefer since its smaller”
32 “Now its time to create the new view”
40 “now its back to Inter face Builder”
183 “you might miss when its over”

superfluous apostrophe:
29 “and change it’s text to read ’Original Value’”
29 “and change it’s title to be ’Edit’”
81 “Each view controller gets it’s own tab”
167 “or passes it on to it’s nextResponder”
186 “last (on top) because it’s zPosition is set”

It would be rather helpful, in chapter 2, to give an illustration summarizing what we are going to do before we do it. Show both controllers, both xib files, and the relationships between then. Then, describe how to make these files. As it is, I feel like I’m just blindly wandering about, with no sense that of our overall goal.

The step to customize the Xcode Toolbar does not seem to be necessary for people who have just downloaded Xcode, since it seems to be included in the Toolbar by default now. So, you may want to acknowledge that this section may be skipped if people already see the Overview pulldown in their Xcode toolbar.

in last paragraph:

now—>Figure 1.4, on the next page shows the Overview item being dropped on the left side of the toolbar.

correction—>Add a comma after “on the next page”

In the first paragraph: References to “the list” actually refer to the file list on the right side below the toolbar. However, there is no prior reference to this area, so the reader is left to mistakenly infer that “the list” refers to the “resource” list on the left. There seems to be a few missing sentences between the first sentence and the second sentence of this paragraph.

I would also suggest using the term “Groups & Files” list instead of “resource” list so that it is easier to match up with the actual Xcode GUI.

Overall, this paragraph should be rewritten to be clear as to which area the clicks are occurring in and which area things are being displayed.

missing comma after “refactoring” and missing period after “etc” in “refactoring, etc.”

The button is labeled “Build and Go”, not “Build & Go”.

could also use more commas, such as after “Now that we have our whirlwind tour of Xcode ” and “In order to make that happen though ”

“lets run” should be “let’s run” (missing apostrophe)

would be better to say “another one of the major tools” instead of “another of the major tools”

“UIs” not “UI’s” (should not be possessive)

also, more commas would be helpful:
sec 1.3, para 1, line 3: as the name implies
sec 1.3, para 1, line 7: As with Xcode
last para: Once the simulator launches

“Open the HelloViewController.xib by double clicking on it in the Resources group in Xcode.”

The file can be opened by clicking on it anywhere (in either the left “Groups & Files” pane or the right “File Name” pane (if either the project or Resources is selected)). So, the above instruction is confusing and unclear as to what to do where.

The instructions for configuring the label fail to mention that the label must be the item selected. It is easy to accidentally deselect the label so that the Attributes inspector, for example, is actually for the background/view and not the label itself. A screen shot of the related Attributes inspector would be helpful.

Figure 1.5 shows the library, not the IB Attributes Inspector, so the caption is incorrect.

“XML equivalent” is probably more precisely expressed as “XML version” or “XML-formatted”

missing comma:
Since the nib file type has been around since Mac OS X 10.0(and even before in NeXTStep)and .xib is relatively new people still refer to them as nib files.

missing commas
Before we dive into the code
Once you have selected a file in the list

The two missing apostrophes mentioned in #35113

from the preceding page, it states: “Figure 1.7, on the following page shows”

Since the words “Figure 1.7, on” was on page 17, I interpreted “the following page” to be page 18, but the figure is on page 19. Would be better to specify “Figure 1.7, on page 19, shows” (also note the comma after the page number)

“superview” is used without explicitly explaining what it is.

“If its easier to find what you are looking for you can
hold down the option key and click and Xcode will display the symbols in alphabetical order.”

The above sentence is confusing. It does not tell you that you need to be clicking on the symbols pulldown. It should also be rewritten to explain at the beginning the purpose of this alternative.

For example: If it would be easier to find the symbol from an alphabetical list of symbols, you can option-click the symbols pulldown, and Xcode will display the symbols in the code in alphabetical order.

You can add a special feature to explain to people who don’t know how to “option-click” or “control-click” something so that you can use these more concise terms in the rest of the book.

This page has figure 1.7, but the label and caption is missing for the figure. In addition, the screen shot should be annotated so that it is clear what parts are the struts and what parts are the springs.

It seems like a waste to have a single screen shot take up the entire page. Perhaps 3 screen shots, one showing struts on, one showing springs on, and one showing a mix would be a better use of the space. Or step-by-step screenshots from the default setting to the desired setting (take off two struts and add two springs).

initWithCoder function indentation closing the if statement and return are tabbed in an extra tab.

“For the common case there will be just one section, but when multiple sections are called for the UITableViewDelegate protocol provides methods that let you customize header and footer views for each section, naming and demarking what their rows represent.”

I had to re-read the above sentence 3 times before I understood it… Shouldn’t there be a comma after “called for”?

I have just worked through the first two chapters. Note I have worked through the Apple tutorial as well.

Content wise the first couple of chapters is good. But I think the Apple approach of working through the basic “hello world” type program without using a predefined template is instructive. I think this should be part of the first chapter.

Some parts of the book are also a bit wordy. eg:
You really did your first VC in the Chapter 1, Hello iPhone, on page 9
but we did not spend any time going into the details as we were too busy
building our first iPhone app. When you wanted to enable rotation for
your first application you made a small modification to the subclass of
UIViewController which we called HelloViewController.

That first sentence could have stopped after “page 9”. This is pragmatic after all. Concise sentences please!

missing commas (and apostrophes mentioned in #35113):
Once it’s launched

Once its done compiling, packaging and signing your application

Once its started

Congratulations

“choose the Properties tab”
This tab does not exist if person has a new install of Xcode and has not setup devices/provisioning profiles. Assuming that many of the readers will be in this situation, there should be a mention of what is “wrong” if one does not see the Properties tab.

You do not explain why one should choose between making a specific provisioning profile for use with the examples in the book versus using an existing profile. A person who is new to all this would not know what factors to consider in deciding which way to do things.

The screenshots and text should be updated to reflect the selection of OS 2.1 (which is what people who have just downloaded Xcode see).

I agree with others that it is very disappointing that the steps for getting to the point where the provisioning profile is installed properly are completely skipped. If it is too long for the text, perhaps an Appendix would be a place to put it. Given this is supposed to be targeted for people who have not developed for iPhone before, this is a big gaping hole. By not adding the steps, readers are forced to spend a lot more time to get this last step working. Thankfully, in your discussion forum, someone had pointed to a URL that was very helpful for getting this set up.

the first line of page 70 reads:

“The main task of our navigation control is to maintain the stack of
view controllers.”

I believe it is a NAVIGATION CONTROLLER, not navigation control.

“In Inter face Builder’s Library palatte, type “text”"

palatte -> palette ?

On page 59, we’re told to drag a Navigation Item into the Inspector and then connect it to the File’s Owner’s navigationItem outlet. However, as far as I understand it, this is only possible after the AddTeamViewController.m file has been created and the File’s Owner’s Class has been set to AddTeamViewController, which is what we’re told right afterwards, on pages 59 and 60.

So in order to get this working, you’ll first have to create the Class File and its contents, then tell File’s Owner the correct Class name and then add the Navigation Item.

First things first we’re creating a new instance of AddTeamViewController.

Remove “First things” or put a colon after the second “first” ?

In the first paragraph, the sentence “Once we’ve entered the name and press save,…” should instead be “Once we’ve entered the name and pressed save,…”.

In the code sample, rather than calling the tableView method directly, why not use the tableView property instead? So, the code for notifying the UITableView object of a change would look like:[self.tableView insertRowsAtIndexPaths:[NSArray arrayWithObject:indexPath] withRowAnimation:YES];

In the viewDidLoad method, you set the UITextField delegate and return key type on the text field programmatically when both can be set easily in IB, the latter through the same technique shown in the previous chapter and the former through a simple control-drag from the text field to the File’s Owner object in the inspector. I think it would be better to do everything possible through IB.

Would be nice to have the keystroke sequences enclosed in boxes (see page 21) as opposed to just in parenthesis.

It is not really clear where to add the code to the BottonViewController.m file. Perhaps it will be helpful to provide some guidance similar to that for adding code to the .h file (… above the @end directive…). Also, the last line of the previous page should have a colon instead of a semi-colon (…some code that looks like this; )

Need to get rid of the creation of the PlayersTableViewController in code and move it to the nib file.

The book says that sqlite3 is provided by OSX, but I can’t find it anywhere on my system. Did the author already have it installed from an outside source, and just think it came preloaded?

Missing . (dot) in the last sentence of the first paragraph in chapter 11.2.
“All the drawing, animation and other visual features of a view are directly
or indirectly handled by the layer ” <- no dot

AddTeamViewController.xib

Connecting the File’s Owner to the Navigation Item doesn’t work.

You either need to move this to section 3.12 and add additional information about adding a navigation item outlet, or move the section on creating the AddTeamViewController class to this section and explain how to add the navigation item outlet. Once the class and navigation item outlet have been created (and the class assigned to the File’s Owner) the existing paragraph will work.

A double “that” in a sentence (middle of the first paragraph).

" In March, measurement firm M:Metrics said >>> that that <<< their studies showed that 84.8 percent of iPhone users said they accessed news and information with their phones, as compared to 13.1 percent of the overall mobile phone market and 58.2 percent of smartphone owners ."

All bullets in the bullet list on the bottom of the page have File’s Onwer instead of File’s Owner.

Section 3.10 looks to be missing the @synthesize for the addbuttonItem.

First paragraph, last sentence, you have, “You just have add …”. Should be, “You just have to add …”.

Second paragraph, 4th sentence, you have, “You can create custom subclasses that you adopt …”. I think you want to say adapt instead of adopt.

It would be helpful if common mistakes that people run into might be mentioned at each step and the solution provided.

I, for one, missed adding the both on page 59 (since it wasn’t mentioned explicitly) and also on pages 33-34. While everything compiles, I did not understand why the outlets were not being recognized in IB. So, a tip to the user (at page 33/34) would be that if the outlet isn’t being recognized when the class is set for the File’s Owner, then check to make sure that the class has indicated that it is implementing whatever the particular protocol is.

Last paragraph, second sentence, you have, “It turns out, as usual, that’s
it’s …”. You probably wanted to say “that” instead of “that’s”.

Second paragraph, first sentence, you have, “Our AddTeamViewController views needs …”. The word “views” should be singular.

“We want a table view in this case, so delete the view and replace it with a UITableView.”

It would be helpful to be more explicit about how to perform this step. Deleting the view object and adding another view object does not change the view object from the default one provided by IB. Instead, one can set the class of the view to be UITableView in the Identity tab for the view object.

Would be helpful to note to readers that if one does not see the “view” outlet after assigning the File’s Owner to be PlayersTableViewController (so that one cannot assign the table view to be the File Owner’s view outlet), then one has forgotten to specify that PlayersTableViewController is a subclass of UITableViewController (since Xcode makes it a subclass of UIViewController by default).

“You could run this code now but your player’s table view will be empty because we haven’t implemented its UITableViewDataSource methods yet.”

This above sentence seems to discourage readers from trying to run the code. It seems to imply that it would not be worthwhile to try running the code now. It would be better to rephrase it so that it encourages readers to run it (and therefore debug up to this point).

As noted in #34847 for B2.0, you need to add
#import “PlayersTableViewController.h”
to the top of “RootViewController.m”
in order to be able to run the code.
This should probably be mentioned and shown at the beginning of 4.6 (on the previous page).

In the last paragraph, second sentence, you have, “You’ll use this techniques …”, The word “this” should be “these”.

In the third paragraph, first sentence, you have, “… six different view controller that …”. The word “controller” should be plural.

The discussion about navigating in Xcode should be a note or some type of other reference as it brakes the flow of what you are trying to describe.

In the second to the last paragraph you reference Build & Go button but most places you also reference the key combination, I think you should mention the key combination is Alt + Command + R. In addition, Xcode uses Build and Go not Build & Go if you want to be consistent. This is also the case on page 15 and 21. On page 20 it is Build & and Go button.

Section 1.5 is the first time you mention provisioning profiles and developer certificates. This was very confusing for me. I think you at least need to provide a definition at a minimum but preferably a full explanation or side bar.

The introduction to chapter 2 is the first time MVC is mentioned and it is not defined. While most readers may understand what you are talking about many may not. Especially other mobile developers like J2ME developers where there is not an MVC. I think this should be defined and mapped to the MVC components on the iPhone some where. Preferably in the first chapter before Controllers are even introduced. This could be a sidebar if it does not fit any other place.

In section 2.1 when you instruct the reader to add a button you might want to be specific and ask the reader to add a Round Rect Button if that is the type of button you want them to add.

Section 2.1 is the first time you mention the nib’s document window. You might want to explain what that is and what you can find in it. You should also probably explain what the File’s Owner object is.

In:

if (editingStyle == UITableViewCellEditingStyleDelete) {
[tableView deleteRowsAtIndexPaths:[NSArray arrayWithObject:indexPath]
withRowAnimation:YES];
[teams removeObjectAtIndex:indexPath.row];

You must call tableView:deleteRowsAtIndexPaths: the first and NSArray:removeObjectAtIndex: the second.

on the last sentence on the page, you have the word “fiver” instead of “five”.

In the “Application-Name” bullet point, fourth sentence, you have, “On the actual device device, …”. Too many device’s.

The code list on this page may not have enough context. I know for example, I originally put the header file line inside the {} and got compiler errors. So it may depend on how experienced with ObjectiveC you assume your readers have.

In section 2.3, outlets and actions are used but not defined.

In section 2.3 it states “go back to Interface Builder and you’ll see the action and the two outlets that you just added”. You might want to tell the reader where they will see that.

In the last paragraph, second sentence, you have, “… since that’s what what …”. You should remove the second “what”.

In the fourth paragraph, second sentence, you have, “Like most databases, works with SQL …”. I believe you wanted to say, “Like most databases, sqlite3 works with SQL …”.

Using what I think is the latest version of the iPhone SDK, the method cellForRowAtIndexPath is already defined using a CellIdentifier. The code on page 48 has us create an index called MyIdentifier and then states we do not need to modify any of the other lines. One page 49, section 3.7 the code shows the correct option of using MyIdentifier in the correct places, in contrast to the “not need to modify any of those lines” in the previous page. This could be a little more clear otherwise people could miss it. You may also want to mention removing the original CellIdentifier NSString though it really does no harm.

Thanks!

Mike

In the second paragraph of section 2.7, I am confused by the statement, “Select the new view controller and open the Attributes inspector”. Maybe I am just confused by the new part since the previous paragraph asked me to open the original controller.

The method declaration for handleGoClicked: should be of type IBAction so that it can be easily hooked up in IB.

- (IBAction) handleGoClicked: (id) sender;

When it says ‘Navigate to SDKs/iPhoneOS2.0.sdk/usr/lib/’ I can’t find SDKs/iPhoneOS2.0.sdk/usr/lib/ giving a full path (/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS2.0.sdk) instead of a relative path would be more useful

In the first paragraph, second sentence, you talk about popping events off of the stack when actually is is dequeueing from the queue.

Last paragraph, first sentence, you have, “… as they are popped of the
event queue.” The word “of” should be “off”.

I think section 2.4 Configuring the Text Field should go at the end of the chapter. At that point you have something with a text field you can play with. I know I read the whole chapter and then had to go back to figure out how I was going to play with the keyboard.

In the second paragraph, you talk about a previous tap example that we have not seen yet. I am assuming that this refers to a section you have not added to the book yet.

In the paragraph after touchesMoved:withEvent:, second to last sentence, you have, “When the one or more …”. Remove the word “the”.

First paragraph, first sentence, the abbreviation “etc” should have a period after it. A quick search of the PDF shows inconsistent punctuation for “etc” in many places.

First paragraph, second sentence, you have, “… and still get some much done …”, The word “some” should be “so”.

In the first paragraph, second sentence, you have, “There are several built in transition animation that …”. The word “animation” should be plural.

Second paragraph, first sentence, UIView should be plural.

Second paragraph, second sentence, you have, “CALayer’s are order on two properties …”, The word “order” should be “ordered”.

Second paragraph, third sentence, you have, “… then they are order according …”, The word “order” should be “ordered”.

In the second paragraph of 4.3 “The Back Button” theres a sentence that reads:

“…you create a new instance of
the appropriate view controller class and then pop it onto your navi-
gation controller’s stack of view controllers using the navigation con-
troller’s pushViewController:animated: method”

I believe what was meant to say is that you PUSH it onto the navigation controller’s stack of views. Popping it would be going back in the hierarchy, but what is described here is pushing a view from a selected item.

I just finished reading chapter 4.

At the end of the chapter we add an edit button to our PlayersViewController.xib file using interface builder. We dragged a bar button item, set its title to “Edit” and connected it to an action. But after reading that, and from what I understood, its much better to add an edit button programatically because of the instant functionality I am given.

When I add it via interface builder I must manually assign it to an action and handle the editing myself, if I add the button programatically its automatically added to the navigation bar, has a title assigned to it and can handle editing immediately.

But, in interface builder when I added the bar button item there is a drop down in the attributes tab of the inspector, that lets me pick the button type. Isn’t this the same as adding it programatically? or is it just so it sets the button image and title?

Is there a way to achieve the same thing with interface builder or just with code?

And one final question, in what cases should I create my own edit button and handle how it responds on my own, instead of using the button thats ready to implement via code?

ViaFelipe Laso

In the code sample, the test should be triggered if the event.allTouches.count equals 2, not if it is not equal to 2. Aside from being in accordance with the way multi-touch is handled (keeping a full set of all active touches until one or more are discarded after touchesEnded), it also prevents a rather nasty NSRange exception on line 5 of touchesMoved where the user lifts a finger and then moves the remaining one.

“Next we need to add the outlet and property we will use to interact with the text field on the modal view we are about to create.” I suggest adding something like: “And we need to tell EditorViewController to implement the UITextFieldDelegate protocol.”

In Objective C Properties box
We don’t have space in this book to do a through
explanation

Should be “thorough”?

“Which ever” should probably be “whichever” (sidebar, “Which ever approach you take”)

I’m not sure yet, but I think this text:

“Select the new view controller and open the Attributes inspector (Command-
1). Set the nib file name to Editor and then set the class name to Edi-
torViewController.”

Would be more clear if it noted that you set the class name in the Identity Inspector (command-4). Unless I have it wrong, but there’s nowhere to set the class name in the Attributes Inspector.

In the fourth paragraph, “mimick” should be “mimic”.

section 3.2, paragraph 3, line 2:

“play this roll”

should be

“play this role”

3rd Paragraph, 4th sentence. “By convention the idenfier” should be “By convention the identifier”

The sample program doesn’t work as printed.
The following line:
indexPath = [NSIndexPath indexPathForFow:[teams indexOfObject:teamName] inSection:0];
gives a compilation warning:
/Users/Frank/Documents/iPhone Projects/BasketballTeams/Classes/RootViewController.m:201: warning: ‘NSIndexPath’ may not respond to ‘+indexPathForFow:inSection:’
and also at runtime it crashes at that point.

I do see - in the documentation - that the method +indexPathForRow:inSection: is part of the NSIndexPath UIKit Additions. That might give a clue what to change to make the sample compile and work.

I would strongly suggest Aaron HIllegas Cocoa Programming (isbn: 0-321-50361-9) for an excellent explication of properties.

I just downloaded the latest version of the SDK (I think), and in the code fragment, *MyIdentifier is actually *CellIdentifier in the pre-generated code.

I just downloaded the latest version of the SDK (I think), and in the code fragment, *MyIdentifier is actually *CellIdentifier in the pre-generated code.

It seems to me that this should tell us to choose the Device-iPhone OS 2.1 item, rather than the 2.0.

You should explicitly tell us to turn on the text centering, otherwise the rotating behavior seems like a bug.

In the second paragraph there is a sentence that reads:

“The cool this about this though is that
the magic is not really magic”

I believe its “the cool THING about this tough. . .”

Lots of talk about making your own button and then re-using it, but it’s not quite clear (yet?) how you’re supposed to do it. Maybe a bit more on this would be useful…

“If you have more than five controllers the tab controller places the first for and …” => note the last “for” should be “four”.

Hey, I’d really like some more information about how to do a custom UITableViewCell. You don’t cover that.

Thank you.

for the Inspector the command is:
command+shift+I

(in the PDF is command+shift+1)

I think the defaults may have changed, but the table rows already resize by default. That is, my view never matched Figure 3.4 — the rows were always expanded… and Figure 3.5 — it’s already set up that way when I open the nib file.

“File… then choose UIViewController subclass” should read
“File… then choose UITableViewController subclass”.

Although the overall book is great, i think explaining the “limitations” of both iPhone and its SDK (storage limits, memory limits etc.) before starting to explain other subjects may be a great addition for readers…

“Add a table view and connect its data source to the File’s Owner object.”

For clarity,

“Add a table view and connect its dataSource and delegate outlets to the File’s Owner Object.”

There are several code statements throughout the book that make unnecessary references to ‘self’. The sorting methods in StatesAppDelegate contain [self.states sortedArraysUsingDescriptors:…]. The reference to ‘self’ is unnecessary here. Sending a message directly to the ‘states’ NSArray variable is sufficient. [states sortedArraysUsingDescriptors…]. The use of dot syntax is confusing for those without a deep understanding of Key Value Coding.

The ‘states’ method defined in the By[property]ViewController classes is used like an ivar instead of a direct method call. KVC and dot syntax makes this possible at the loss of clarity in the source code.

For style and readability reasons, it is appropriate to declare the ‘state’ method in a separate Category as it is not declared in the Class header file. Using [object message] syntax will make the sorting code more readable.

For example… this is how I re-wrote the code for ByAreaViewController.m

#import “ByAreaViewController.h”
#import “StatesAppDelegate.h”

@interface ByAreaViewController()

- (NSArray *)_states;

@end

@implementation ByAreaViewController

- (NSArray *)_states {
\treturn [(StatesAppDelegate *)[[UIApplication sharedApplication] delegate] statesByArea];
}

- (UITableViewCell )tableView:(UITableView)tableView cellForRowAtIndexPath:(NSIndexPath *)indexPath {

static NSString *CellIdentifier = @“StateCell”;

UITableViewCell *cell = [tableView dequeueReusableCellWithIdentifier:CellIdentifier];
if (cell == nil) {
cell = [[[UITableViewCell alloc] initWithFrame:CGRectZero reuseIdentifier:CellIdentifier] autorelease];
}
// Configure the cell
\t[cell setText:[[[self _states] objectAtIndex:[indexPath row]] valueForKey:@“name”]];
return cell;
}

No context is provided for the code snippet at the top of the page. It would be helpful to place it in the context of the createData method introduced (without explanation) in the applicationDidFinishLaunching method of the SatesAppDelegate.

decent book, I am more of a visual learner and I think you could have easily explained the table view schema in one diagram. In general more visual stuff would save readers like me a lot of time from rereading on what we could grasp in one glance at a diagram that shows the relationship. thanks
Salim Madjd

In the sentence “There are three ways to view
the list of items, you can look at just the icons, which is they way
most experienced UIKit developers prefer since its smaller and they
recognize the icons.”, the phrase “…which is they way…” probably should be changed to “…which is the way…”.

Surfface -> surface

@synthesize addButtonItem; Is not listed as one of the things to perform before building.

The image on page 27 seems to be using a dated version of IB. Then again, I could be using a dated version and the authors a updated version. I would hope that the published book is written for the most current version of Xcode and IB and if not a note to the versions of each mentioned in the preface.

Clicked on StarterViewController.m to open sample text.
In comments is called:
// StarterAppDelegate.m

“Select the new view controller and open the Attributes inspector (Command-1). Set the nib file name to Editor and then set the class name to EditorViewController.”

“Set the class name to EditorView Controller” is not clear. Partly because the class field is on a different screen, under Command-4. I had to download your code to figure out what you meant

At bottom of the page in the code example, a method definition reads:

-(void) conection:(NSURLConnection *)connection

“conection” is misspelled.

My Table View Size window differs from yours in 2 ways:
1) Under Frame, the width and height are the same values (320 and 460) but are greyed out - can’t be changed.
2) I can’t select the Springs. When I click on them nothing happens.

Little confusing to have sample code on 53 and then same sample code on 54 with additional code inserted. Could be done at same time followed or preceded by explanation.

Drag an instance into our AddTeamViewController “Document” window.

Text says Inspector where it should say Document.

in the AddTeamViewController object inspector window —> in the AddTeamViewController document window

Build failed.

Need #import “AddTeamViewController.h” in RootViewController.m.

Somewhere in the description it would be useful to mention that the new Bar Button Item should be control clicked and connected to the File’s Owner for the editButtonWasPressed action

Last line now reads:
/etc/apache2/others/bonjour.conf.

should be (at least on my machine):
/etc/apache2/other/bonjour.conf.

- (void)addButtonWasPressed;
should be - (IBAction)addButtonWasPressed; It should use the Target/Action paradigm that was mentioned on page 33

“the idea of outlets and actions are probably foreign” should say:
“the idea of outlets and actions is probably foreign”

“We don’t have space in this book to do a through
explanation of Obj-C but…”
should be:
We don’t have space in this book to do a thorough
explanation of Obj-C but…"

Hi, in the code you have double coding styles within the same if-sentence:

if(nil != editorViewController.field.text && [editorViewController.field.text length] > 0)

If you would stick with your first style, the second part would be 0 < [editor…], but I think you should stick to the second style as it is more straight-forward to read. Reading from left to right, the sentence becomes: if editorViewController’s field is not nil. That is a good sentence. You write: if nil is not editorViewController’s field. While technically it’s the same, reading it the way you’ve written is more confusing. Keep the book consistent and decide one one style, preferably the style that’s easier to read.

Oh, and PragProg uses hyphens all over the place in many of their books. Doe-sn’t look good at all and int-errupts the rea-dingflow. I hope you can just uncheck this style, it even breaks up your code in places (like dismissModalViewControllerAn-imated: on page 38)

Great book, guys, keep up the good work! :) Can’t wait to have it in my hands :)

Cheers

Nik

Should explain or have discussion on ‘nonatomic’ and ‘retain’ and any other parameters passed in ‘@property’

Thanks Greg

‘just build’ should be ‘just built’

Second paragraph in 2.6 is not clear to me why I would do this. I would like a longer discussion about why I am doing the steps indicated.

Thanks

Greg

‘to managing’

should be either:

‘for managing’ or ‘to manage’

‘passed in the’ should be ‘passed the’

Last paragraph unclear why I am doing the steps indicated. would prefer longer explanation or discussion.

Thanks

Greg

‘we us’ should be ‘we use’

‘a application’ should be ‘an application’

Section 3.8: Supporting rotation was unnecessary when I ran through it as the table seemed already set-up to support proper rotation.

The very last character on the page should be a colon. It is currently a semi-colon.

In the viewDidLoad method in section 3.9, XCode generated the editButtonItem on the right side of the navigation bar:

self.navigationItem.rightBarButtonItem = self.editButtonItem;

This could cause confusion in the next section where you instruct users to put an add button on the right side..

IB will not let me connect File’s Owner to the Navigation Item until after I set up the ViewController class and assign File’s Owner to be of type AddTeamViewController. But the instruction to connect it comes before creating the class in the book. -VincentV

2.6 The Editing View Controller in Interface Builder

Open the StarterViewController.xib document if you closed it. From the
Library drag out a View |space| Controller into the document. Your window should look something like Figure 2.7, on the following page <—missing period here

next paragraph org text
Select the new view controller and open the Attributes inspector (Command-1). Set the nib file name to Editor and then set the class name to EditorViewController.

edited text – version 1
Select the new View Controller by clicking on its icon in the ‘StarterViewController.xib window. Next, open the ‘Attributes inspector’ (Command-1) and set the nib file name to Editor. Then, open the ‘Identity inspector’ (Command-4) and set the class name to EditorViewController.
edited text – version 2 – referencing dropdown menus
Select the new View Controller by clicking on its icon in the ‘StarterViewController.xib window. Next, open the ‘Attributes inspector’ (Command-1) and select the nib file name Editor from the nib dropdown menu. Then, open the ‘Identity inspector’ (Command-4) and select the class name EditorViewController from the class dropdown menu.

A bit about refactoring in one of the early chapters of the book would be nice.

Would be nice to have the swipe to delete function explained for tables.

In reading chapters 6 and 7, I feel like a significant amount of relevant code was skipped in the discussion. I realize that at some point, we need to leave the safety of the nest and venture out on our own, but I, for one, enjoyed and appreciated the detailed walk through of the earlier view controller chapters. Considering how many different elements there are to creating an iPhone app, the audience would be well served to have the detail walk through. Anyways, just my two cents. Thanks!

this is a note for the v-bdiphone-v-01.mov… not sure if it effects the book or not…

at timecode: 15:01 talks about Style being set to “Indexed”, my version of IB lists “Plain” and “Grouped” not “Indexed” for the table view.

this is a note for the v-bdiphone-v-02.mov… not sure if it effects the book or not… at timecode: 18:51 a line of code (#import “IngredientsViewController.h”) pops on the screen with no voice over noting that it has been added to the project file, and without it, the app will not compile and you get a ‘request for member “ingredients” in something not a structure or union’ error.

There is no mention of centring the label in the 1.3, which makes the rotation later on not work as expected.

Control click on the button and drag to the File’s Owner object.

I don’t know if this means to control click on the button in IB and drag it to the Files owner. If it does, then it does not work for me. Maybe a better description or an image of what to control click on.

In section 3.12, the following text is confusing. I have reread it about 10 times and I am not sure what it is trying to tell me:

“We need to do two things back to the view controller: The text field and the view that contains the text field.”

Remove the errant period after passing in:
“We switch to our team adding view by calling pushViewCon-
troller:animated: on our navigationController, passing in. the AddTeamView-
Controller.”

Sentence should not say everyone, but everything: “That was a bit of work but we’re done with everyone we have to do to add a new team to the list.”

re: Simplest technical fix for “Can’t connect File’s Owner to Navigation Item” problem.

Two parts to this fix: (1) remove one sentence in section 3.11, and (2) perform that task two pages later in section 3.12.

(1) On page 60, the fifth paragraph of section 3.11 (starting with “Our AddTeamViewController…”), REMOVE the following sentence:

“Control click the File’s Owner to the “Navigation Item” and assign it to the File’s Owner’s navigationItem outlet."

As others have noted, this task cannot be performed until the class files have been created.

(2) Insert that sentence at the END of paragraph 2 in section 3.12. Now it will work well (after defining the class in Xcode and making File’s Owner set to AddTeamViewController.

Yay. :-)

After typing “sqlite3 shopping.db” in terminal - the book says “This creates the shopping.db file if it doesn’t already exist.”

I don’t believe the file is actually created until something is written to the database (e.g. a table is created). Not a huge problem, but if someone happens to go looking for it after they execute the given command it’s not going to be there.

You bring up attributes inspector in IB 3.1 with Command-1, not Command-Shift-1.

You bring up connections inspector in IB 3.1 with Command-2, not Command-Shift-2.

I believe it would be better to for “Open it and add some code that looks like this;” to have a colon (:) instead of a semicolon (;).

Also, to verify what another reader said, the “it’s” and “its” throughout the book are often interchanged.

The general rule is : when you want a contraction, “it’s = it is”, and any possessive (belonging to ‘it’) is “its”. It seems counter-intuitive, but I’ve never forgotten this rule since one of my high school keyboarding classes - an assignment where I mistakenly put an apostrophe on its caused an A to become a B-. Lesson learned. ;)

The word in the section on Objective-C Properties should be “thorough” instead of “through”, as in “We don’t have space in this book to do a thorough explanation…”

The reader is asked to link up the Navigation Item to the File’s Owner’s navigationItem outlet. This outlet isn’t available at this stage as the File’s Owner is set as a subclass of NSObject. We have to first create the AddTeamViewController class in InterfaceBuilder and set the File’s Owner to that. The whole task of adding and linking up the Navigation Item would be better grouped with the linking the other outlets on the next page.

The code example for setting a nav item’s title seems to have a memory leak. Setting self.title should retain the NSString, which if created using alloc/init will already have a retain count of 1. You ideally want to autorelease or just use +stringWithFormat:

In the second paragraph of section 2.2, the sentence “The first view has a UILabel that displays some text and a UIButton that brings up a modal view with a single text field that we can type a new value into” is confusing because the joined clause doesn’t mention the second view. This whole paragraph is somewhat unclear on a first read through.

Under section 5.2 the first two paragraphs are repetitive with regard to the data being hard coded — “in a real world application…”

The code in this section seems to need some help. The code snippet under 5.2 needs to be in the createData method and needs to set the dictionary objects back into the states property. The states property needs to get declared and synthesized somewhere. If you’re leaving this to the reader it might be good to at least mention it and give a hint to the object type to use.

You talk about NSHost, getStreamsToHost:, inputStream:, and outputStream: not being supported on iphone, but I’ve been using this on iphone with no problems:

\tNSHost *host = [NSHost hostWithAddress:@“10.1.20.111”];
\t[NSStream getStreamsToHost:host port:5004 inputStream:nil outputStream:&outputStream];
\t[self openStreams];

The .nib
will now appear in the Groups & Files section of you Xcode sidebar.

The book says that by pressing the ‘option’ key when clicking XCode makes the list of symbols appears alphabetical. For me it didn’t work with the ‘option’ key, but instead pressing the ‘alt’ key worked for me. I downloaded XCode for iPhone yesterday.

Second paragraph, last sentence, you have, “… down to the ”Tasks" section, where find a link …“. Missing the word :we: between ”where" and “find”.

The use of “delegate” as an instance var is misleading. True delegates are not retained and their methods are described in a protocol and checked in runtime. Here we do not have a “classical” Delegate pattern. Much better will be to call it something like tableViewController

In the second paragraph, second sentence, you refer to the (as yet) unwritten chap.tabcontrollers. Isn’t this a reference to Chapter 5, Tab Bar Controllers, which is written?

The first complete paragraph of text says…

“Our AddTeamViewController views needs a title and a button to get back to the list of teams. Search for “Navigation Item” in the Inter face Builder library. Drag an instance into our AddTeamViewController Inspector window. Control click the File’s Owner to the “Navigation Item” and assign it to the File’s Owner’s navigationItem outlet."

This does not work for me. When I Control drag from the File’s Owner it does not allow me to drop on the newly added Navigation Item, or in fact to any of the items in the AddTeamViewController IB inspector window. If I right click on File’s Owner, there are no outlets or actions defined.

Perhaps you missed out some steps, like adding outlets and/or actions, assuming the reader would know to do them? I’m very new to iPhone development and frankly do not know how to fill in the steps that you might take for granted. However, when you specifically state “do this…” and it does not work, I get frustrated.

I am particularly frustrated at this because I’ve been trying for a long time to get a very simple iPhone app to do just this very simple task (slide in a new view controller to add an item to a table), and it just simply never works for me, even though you book and several other references all hint at the same thing. I’m obviously missing something so basic that no text ever describes it, but I do not know what it can be.

I’m using Xcode/IB 3.1.1. although I hope that it has not changed too much from the version you are using. What version of Xcode/IB are you using to validate your example code?

In Figure 3.13, where does the AddTeamViewController File’s Owner Received Action “addTeam” come from? It is not mentioned anywhere prior to showing up here.

The new version of Mail.app has a different way of deleting messages - checkboxes and a global delete button.

”you’ll almost always have your UITableViewController play this roll“ - the word “roll” should be spelt “role”.

“fiver or more” should be “five or more”

Don’t mean to be so nit picky here but …

UITableViewCell *cell;
cell = [tableView dequeueReusableCellWithIdentifier:MyIdentifier];

Can be condensed to…

UITableViewCell *cell = [tableView dequeueReusableCellWithIdentifier:MyIdentifier];

That is all! As always great job and please keep up the good work. You are all awesome :)

If you only add the California data shown in the example you get a runtime error with an index out of bounds in the statesByPopulation and statesByArea methods when you create the NSRange range = NSMakeRange(0, 5) and then apply it to the collection which has only the one member.

In the example application you use a UIView to create the textbox for create Directory. You don’t explain why or how this works. Some explanation would be wise.

I bought your book first and after going over this chapter I thought it was a little weak. So I bought the Core animation book and the chapter in it is almost exactly the same as your chapter. Very disappointing.

On the first paragraph of page 205 there is a line that reads:

“After that, another pair of buttons deter -
mines whether the search applies to all languages, or just Objective-C,
C, JavaScript, and C.”

It repeats C twice, perhaps you guys simply meant C.

On page 214 there is a line that reads:

“At you could click the ”Continue" button to plow ahead and crash"

That first part doesnt make any sense.

In the code samples (specifically I’m looking at the FilesystemExplorer one), in the “Build” section of the “Get Info” dialog box, The code signing identity is set to “iPhone Developer:Chris Adamson” instead of just “iPhone Developer” (like BundlePrefereableClock does). That means that people are going to have to make changes in a piece of the XCode UI that the book doesn’t really talk about in order to be able to run the app on their device.

For Me the overview menu is by default. But the active target is not

Paragraph at bottom of page: “When you mouse up you should see a list of items titled ’Events’ select
the edit action.” should be broken into two sentences.

Change sentence (near bottom of page) “We will discuss the methods in this protocol in a moment, for now know…” to “We will discuss the methods in this protocol in a moment, but for now, know…”

sentence construction : “Control drag from the text field to the files owner object, when you release select the delegate…” might be “Control drag from the text field to the files owner object. When you release, select the delegate…”

I think the File I/O chapter is, by far, the most confusing chapter in the book. I’ve gone through the previous chapters and found them illuminating but I’ve found this chapter to be particularly challenging. It wouldn’t hurt to go through the example application a bit more slowly just like the other chapters. There’s a lot to learn that’s very useful here and I was looking forward to it but it hasn’t been as instructive as the other chapters.

Under 5.3, reminder should read remainder.

Incredibly minor: The sidebar entitled “Target/Action Paradigm” should come after the code sample. As currently laid out, the @end tag from the “EditorViewController.h” sample isn’t readily visible and could be the source of a typo by someone who is either cutting and pasting the code directly, or just following along exactly with each example.

“When propmted…” s/b “When prompted..”.

In the first paragraph of section 3.7:

I believe “and just set the title property to the team name” should be “and just set the text property to the team name”

Last paragraph on the page:

“Our text view’s rows” should be “Our table view’s row”

Also, I’m using the latest Xcode from the 2.1 SDK and this built the project fine. Perhaps this latest SDK doesn’t have the problem with the rows not filling the entire space? My build at this point does not look like Figure 3.4. When I look in the nib all four margins are set, not just the top & left.

My iPhone is on O2 in Ireland, and we don’t have Visual Voicemail here, so the example quoted in the foonote doesn’t work for me. Hitting the Voicemail tab just dials the Voicemail number here,

Missing an @import “AddTeamViewController.h” in RootViewController.m before adding the method (void)addButtonWasPresse. Otherwise AddTeamViewController would be undeclared.

In the second to last paragraph, only sentence, you have, “This sends the String Hello iPhone to stout, …”. “stout” should be “stdout”.

“reorganize to your hearts
content.” should be “reorganize to your heart’s
content.”

third paragraph: “(completion, refactoring etc).” should be “(completion, refactoring, etc.).”

In the paragraph beginning ‘Our AddTeamViewController…’ you can not ‘Control click the File’s Owner to the “Navigation Item”…’ until you have created the controller class in XCode and set File’s Owner type to the controller type. Nothing happens when you control click.

Section 4.7 seems out of place to me, wouldn’t it be better to do handle it in chapter 3 along with the rest of the table view stuff?
I feel it kind of distracts from the navigation stuff handled in chapter 4…

in section 3.2, first paragraph, last line: “reordoring of rows” should be “reordering of rows”.

“play this roll” should be “play this role”.

“Though you could set any object to serve as a table view’s data source, you’ll almost always have your UITableViewController play this roll.”

Doesn’t this violate the MVC design pattern? Isn’t the Model supposed to define the data source? And shouldn’t you keep the Model and the Controller separate?

The text says that Xcode News [RSS] can be used to keep up to date with announcements about things like new sample code, but that section of the UI seems to be no longer updated. The RSS feed shows items up until June, and it is now November.

The second paragraph of section 5.2 is just a repetition of what was already set in the first one. I would suggest to use only one of those:

The data for this example is hard coded in the application delegate. In a real world application you’d build out a set of model classes to represent your data and then store that data in a database or file (I prefer a database). For this simple example though we will just use NSDictionary objects to hold the data.

The first thing we need to do for our example is to create the data. In real world applications you would develop a set of model classes that would contain the data and then persist their information into either a database or file. In our case we are going to keep it simple and just use NSDictionary and hard code the data. Here is the code for the California data;

Missing opening bracket in sentence:

You can see a screen shot here Figure 5.3, on page 91).

Repeated use of ‘lets’ without an apostrophe.

Last paragraph, middle of the second sentence reads: “….. the tab controller places the first for and replaces whatever would have been in the fifth place…..”. Should read “… the first four …..” I think.

First paragraph line 4:
“an array of NSIndexPaths we us NSArray’s arrayWithObject: ”

Replace “us” with “use”.

Second paragraph, first line:
“That was a bit of work but we’re done with everyone we have to do”

Replace “everyone” with “everything”.

Section 3.11 onwards describes how to create a .xib file from scratch, and later hook it up to a controller class.

I wasn’t able to follow the text in this direction. But if I create the controller class first, and then the xib file, I was able to hook everything up correctly (i.e. add navigation item, place the hook from the file’s owner to the nav. item, set the view as the “view” on the file’s owner etc.).

So the section describing the creation of the controller class should be before the creation of the xib.

“just set the title property to the team name”

should be “text” property

While this shows an example of a modal view, the question I was left with was “Is this how I link all views from a button?” In other words- I’ve seen Apple examples about addSubView- how does that differ from modal? Why would I choose model over the addSubView? It would be great if this section could provide a bit more meat around the differences here, or at least an explanation as to why one would want to use the modal view approach.

The word ‘hierarchy’ is mispelled in the ‘Joe asks’-section: “heirarchies”, “hieirarchy”, “heirarchical”

Typo with the word ‘implementation’ at the end of the page:

“The default implemtentation returns YES, in other words responds
to the rotation event,…”

Page 53/54: Didn’t get the ‘broken’ TableView after the rotation even though I hadn’t made the suggested changes in Interface Builder yet. The default autosizing settings for the TableView now seem to include these changes.

Typo in the word ‘prompted’ (lower part of the page):

“In Xcode select FileNew File… (or Command N ). When propmted choose
a UIViewController subclass that we’re going to call AddTeamViewCon-
troller.”

Between “passing in” and “the AddTeamViewController” there is a tiny little dot that shouldn’t be there:

"We switch to our team adding view by calling pushViewCon-
troller:animated: on our navigationController, passing in. the AddTeamView-
Controller.

Right in the middle of the page:

“We want to be able to pass control over to the AddTeamViewController
now. This will happen with the Add button is pressed. Add the following
code to addButtonWasPressed.”

Should be: ‘(…)This will happen when/if the Add button is pressed.(…)’

Redundancy at the beginning of 5.2:

“In a real world application you’d build out a set
of model classes to represent your data and then store that data in a
database or file (I prefer a database). For this simple example though
we will just use NSDictionar y objects to hold the data.”

… and just one line later:

“In real world applications you would develop a set of model classes that
would contain the data and then persist their infor mation into either a
database or file. In our case we are going to keep it simple and just use
NSDictionar y and hard code the data.”

Since the web is getting more RESTful, it would be wonderful to have some ideas on the best way to fetch/parse data sets from the web. Example, I want to RESTfully fetch arrays of hashes from a database. Should I use several CSV calls, or try to parse JSON/XML? Any best practice on how to map those data points into ObjC structures, or even shove it into a SQLite DB first, and fetch the results as objects? Thanks!

For now you
have just written the inter face—for now that’s all you need

Double ‘for now’ looks bad.

Third paragraph ends “Next we’ll create the interface for this table view controller.” This sentence should come after the following code as I initially thought the following code was creating the interface, whereas it is in fact the code to add the variable ‘team’.

“the tab controller displays a navigation controller that lists the reminder of the controllers along with”

is ‘reminder’ supposed to be ‘remainder’? Either way it might be an awkward sentence.

“The cool this about this” likely meant to be “The cool thing about this”

In Chapter two section 2.1 Your First View Controller, some of the steps to create a move me button application are missing or wrong. first you can not connect Button Click action to file owner until you declare the event action in view controller.h file , first you have to declare and define the action receiver method in view controller files (.h and .m) then you just simply chose the event like TabDown and drag it to the file Owner object . please check the code and the steps .

* Change delcartion to declaration in the following paragraph.

addTeamNamed: is going to take one argument of type NSString. With the delcartion added, RootViewController.h will, in its finished state, look like this:

sentence beginning: “If you are providing more granular infor mation like how far your use rode her bike then the location updates can be more like 100 meters.” should perhaps be: “If you are providing more granular information like how far your user rode her bike, then the location updates can be more like 100 meters.”

Top of the page, middle of first paragraph: implmentation (missing an ‘e’)

You alloc an object (UIBarButtonItem), you have to clean it up. This is a memory leak. Please add autorelease or flesh out the code by adding a variable and releasing it after.

Bottom of this page, continued to page 58:

You alloc an object (UIBarButtonItem), you have to clean it up. This is a memory leak. Please add autorelease or flesh out the code by adding a variable and releasing it after.

if-statement at the bottom of the page is unnecessary .

if (directoryContents != nil)

To quote Aaron Hillegass in his book Cocoa Programming For Mac OS X, 3rd Ed.:

“In Objective-C, it is okay to send a message to nil. The message is simply discarded, which eliminates the need for these sorts of checks.”

Why override the initializer when Apple has provided us with:

- (void)awakeFromNib

which is called on every object as it is reconstructed from the nib file. Both ways work, but your point is “Because it’s loaded from a nib file…” so I think it’s best if you use “awakeFromNib” which is designed for this situation.

Please explain the long-term goals of using the initWithCoder because I think you might have some in mind. (serialization or the ability to programmatically initialize).

Apple’s documentation in the TableView Programming Guide removes the data from the array before deleting the row. Done this way, there is no need for [tableView beginUpdates] and [tableView endUpdates].

Perhaps this is just the safest route to take for teaching people new to the platform? Maybe you could put in a word about these wrapper calls, explaining why they might or might not be used?

Don’t use valueForKey: unless you want to get into key-value coding or talk about it in text and link to Apple’s Documentation.

The errors people are focusing on here can be easily corrected if y’all add an extra step on page 61. Just say to set file’s owner (for AddTeamViewController.xib) to RootViewController et voilla! — instant access to that handy (inherited) navigationItem outlet.

Never mind my previous post. I read a bit farther and I think I see where you guys are going with this. You guys are missing some key steps just about here. :)

Why does your example declare a directoryTableView when it’s a subclass of UITableViewController which has an IBOutlet called tableView which is what Apple’s template Navigation-based project uses in IB?

Can you make it a little clearer that the accessoryButtonTapped… hook is only valid if you are using the UITableViewCellAccessoryDetailDisclosureButton? If a reader experiments and decides they prefer the UITableViewCellAccessoryDisclosureIndicator as it’s more commonly used in Apple’s apps, suddenly that hook never gets called and they will be confused. I think just clarify why you chose to use a button and this hook (As it’s obviously the only option unless you handle multitouch events)

Release that directoryViewController after pushing it on the navigation controller. Memory leak.

Release that fileOverviewViewController after pushing it on the Navigation. Memory leak.

The code is presented two times in a row.

Please tell the user that they need to call updateFileOverview in viewDidLoad. I spent an hour wondering why my UILabels were NULL and not showing my text until, while looking through your code, I realized we are setting the variables before the view has even been loaded.

The Multi Touch example relies on some Quartz API objects and calls to resize the image. I’d like to see more about what Quartz is and how to do image manipulation with it. For seasoned Mac OS X developers, this may be trivial, but for someone like me with previous mobile development experience, but no Mac experience, this part of the example is “magic”.

“If on the other hand your application won’t work with the location service turned on then the user might want the chance to turn it back on from your app.” Should be “…service tuned off then the user…”

“When the system is determining the accuracy of it location fix it takes…” Should be “…its location fix, it takes…”

“Even when two towers are in range the numbers can we off buy quite a bit.” Should be “Even when two towers are in range the numbers can off quite a bit.”

“We take the absolute value because we count going forwards and backwards still traveling” should be “as”

When creating the second NIB I had to set the View’s class to be UITableView otherwise I would get the following error:

* Terminating app due to uncaught exception ‘NSInternalInconsistencyException’, reason: ’-[UITableViewController loadView] loaded the “ByAreaView” nib but didn’t get a UITableView.

This may be caused by another error in my code but the class change rectifies it.

shouldAutorotateToInterfaceOrientation is not commented out now and contains one line of code already. Maybe the text should be more vague here.

All of the projects in Chapter 2 use the View-Based Application template which creates (Hello, Button, Starter)AppDelegate.h and .m, main.m, MainWindow.xib, and other files. The role and function of these files are never discussed. Please try to include a broader discussion so that we can understand the MVC framework that we are using and how these files fit into it. A diagram(s) would be great! It is a huge jump to go from Hello iPhone to view controllers without the context and understanding of the framework. It could be a separate chapter on its own.

Is is possible to add information on how to access the iPhone’s phone number and carrier? This information would allow me to tailor my app to the user.

the browser is useful, but it is not clear how to allow rotation. When I set shouldAutorotateToINterfaceOrientation to YES, the result doesn’t scale to the screen. I couldn’t find example that properly explain how to resize views to fit the orientation.

Footnote: “Note, however, that Shark cannot profile applications that are running on the actual device.” Performance session from WWDC suggests Shark does run on the device. Double-check this.

Would be nice to have material in the Instruments section on diagnosing over-freed objects (c.f., NSZombie)

The first paragraph suggest selecting the Active SDK Device - iPhone OS 2.0. But this may not be correct depending on which OS you have on your device. So first, I think it should say to select the appropriate version that matches your device. Second, I think you might want to explain the SDK concept and how you might need to install new SDK’s to match your device. I know I got bizarre error messages before I knew to install the new SDK and selected the right version.

Section 1.5 really glosses over the certificate and profiling process. I think you should cover it in detail. I am realizing now there are some best practices like using a .* for the app id which Apple does not explain well. I think you have an opportunity to make it clear and make your reader’s transition to iPhone development easier.

Figure 13.1 - The text fields say “Longituide” and “Latituide”.

“Text Traits” should actually be “Text Input Traits”

I would love to see some exercises at the back of each chapter. It would make it palatable to CS professors (such as yours truly) considering adopting it as a textbook.

In the Target Action Paradigm sub-section, the description of the third method signature in the last sentance should read something to the effect: “Finally you might need the last method signature if you are tracking a multi-touch gesture in your app.” The current phrasing is slightly difficult to understand.

The “Build & Go” shortcut described in the 2nd-to-last paragraph is Command+Enter in Xcode 3.1, not Command-Option-Enter

I found this confusing “Control click the File’s Owner to the “Navigation Item” and assign it to the File’s Owner’s navigationItem outlet." I think it should be expanded - something like "Control click the File Owner Icon to display it’s outlets. Drag the NavigationItem outlet to the the Navigation Item.

pop it onto your navigation controller’s stack of view controllers using the navigation controller’s pushViewController:animated: method

—This should read “push it onto your navigation controller” as pop is used in the method to remove the view.

pop it onto your navigation controller’s stack of view controllers using the navigation controller’s pushViewController:animated: method

—This should read “push it onto your navigation controller” as pop is used in the method to remove the view.

Last word, first sentence on page reads “you”, should be “your”.

Section 4.6 Pushing View Controller onto the stack does not indicate to add an import statement to the RootViewController. Running the code after completing 4.6 causes an error.

Need to add #import “PlayersTableViewController.h” to RootViewController.m

The statement “dbFilePath = [documentFolderPath stringByAppendingPathComponent:
DATABASE_FILE_NAME];” returns a string without the “/” before teh database file name.

The folowing files are missing AddPlayerTableViewController.h, AddPlayerTableViewController.m, AddPlayerTableViewController.xib, and BasketballTeamsWithPlayers iin the code/Navigation/BasketballTeamsWithPlayers project.

About midway through paragraph four there is a sentence that reads “In fact, the table needs as many cells are there are visible (or partially visible) cells at any one time…” The are following cells should be as so that the sentence reads “In fact, the table needs as many cells as there are visible (or partially visible) cells at any one time…”

Final paragraph of “Creating a Custom Table Cell Class” section says “In the implementation class, TeamCell.h”, this should be “TeamCell.m”

“Better yet, IB is a tool that a professional graphic
designer could use, leaving the developer (that’s you) to conentrate on
the code.”

“conentrate” should be “concentrate”

In the “Customizing Animations” section you are writing:
“Since we changed the center of the ball image to the bottom of the screen and the animation ends at the top of the screen we get the jump. The fix for that is discussed later in this chapter when we cover key frame animations in Section 12.3, Layers, on page 195.”
But I’m not able to find any fix in section 12.3.!

In general nice book! Always anxious to receive updates with new info!

Nice Greetings

Frank

it says“you’ll see the action and the two outlets that you just added” but I can only see one outlet, the UILabel one.

The paragraph before the last starts with “The same basic principals apply”. The word should be “principles”.

There are question marks for where to find more about properties. Here’s a link to Apple’s site regarding properties: developer.apple.com/DOCUMENTATION/Cocoa/Conceptual/ObjectiveC/Articles/chapter_5_section_1.html

What you could do is point to something like www.pragprog.com/titles/amiphd/links/properties and redirect to the above link as the link may change/move.

The second code snippet has us setting the text field as the first responder in EditorViewController’s viewWillAppear: method. It doesn’t work as the author intends because viewWillAppear: is called before any animation of the view onto the screen. The correct method to give the text field keyboard focus as soon as the modal view appears is:

- (void)viewDidAppear: (BOOL)animated;

This method is called immediately after the view appears on the screen.

Should the TeamCell.xib file be created in the Resources group instead of the Classes group as suggested?

There’s nothing in the text that tells us where the code snippet in the middle of the page (the one that begins with self.addButtonItem = [[UIBarButtonItem alloc]…) is supposed to go.

Which method does that belong to? My initial guess would be in the RootViewController’s initWithCoder: method, but the text needs to make it clear.

The middle code snippet on the page (the one that begins with self.addButtonItem = [[UIBarButtonItem alloc]…) has a memory leak. The call to [UIBarButtonItem alloc] returns an object whose retain count is 1. Assigning it to self.addButtonItem (which actually calls [RootViewController setAddButtonItem:]) increases the UIBarButtonItem’s retain count to 2.

You have to release the UIBarButtonItem in the same block of code to reduce its retain count back to 1 so that releasing it in the dealloc method lowers the retain count to 0 and frees its memory.

I deviated a little bit as far as the colors and fonts were concerned in this chapter and i spent about an hour trying to figure out why the team name and record didn’t display but the division did.. I finally tracked the error down to enabling Bold in the font preferences. Maybe a note somewhere about not enabling bold in the font dialog window would be handy for other people who might try and use some different styles during this chapter..

Chapter 3.12 omits that the File’s Owner object needs its class set to RootViewController (in this case), and the Table Cell itself needs its class set to TeamCell.

If you attempt to set File’s Owner to TeamCell, your program will crash with an exception when it tries to unarchive the TeamCell.xib file because loadNibNamed:owner:options will try to connect your table cell’s outlets to nonexistent variables in RootViewController (self).

Perhaps someone could infer that File’s Owner needed to be set to RootViewController based upon the usage of loadNibNamed:owner:options with owner:self, but I couldn’t. I spent quite some time figuring out where the exception was coming from.

However, I greatly appreciate chapter 3.12 as it taught me something I haven’t seen elsewhere yet!

On line 13 of the code snippet on that page, the value of the assignment, the NSString, is not released after it is allocated. You should either manually release the string on the next line (which would mean you would need a local variable to hold it, or you could use an NSString class method that autoreleases the returned string for you like:

+ [NSString stringWithFormat:]

When you release, select the degate outlet to make the connection.

Typo: delegate instead of degate

That connection will allow the StarterViewCon-
troller can display the editor view controller when the edit button is hit.

Wording…

- (void)viewWillAppear:(BOOL)flag {
[field becomeFirstResponder];
}

This doesn’t work for me. However

- (void)viewDidAppear:(BOOL)flag {
[field becomeFirstResponder];
}

makes the field become the first responder…

As of B7.0, chapter 13 is a decent primer on CoreLocation. Having learned how to work with it from Apple’s docs and various forums, I found the information on how Core Location triangulates the iPhone’s current location to help deepen my understanding of the iPhone’s GPS hardware.

However, it would be great to have a section on the locationManager didFailWithError delegate method, and describe under what scenarios this delegate would be called, what to do when these scenarios occur, etc.

Also, I and other developers on various forums have noticed that the CLLocationManager does not send location updates as frequently as you would think. Specifically, the update interval does not seem to occur at the frequency that you would expect from setting the distanceFilter property.

For example, when I debug the example code on my device, I am only getting 1-2 location updates, regardless of the distance I walk, or what I set the distanceFilter property to. Yet Google Maps is somehow able to get updates at fairly frequent intervals. If you know why the CLLocationManager behaves this way, it would be great to elaborate on this in the book as well.

One minor gripe. The sample code in DistanceViewController.m has this method call on line 40:

[self.locationManager performSelector:@selector(startUpdatingLocation) withObject:nil afterDelay:60.0f];

I don’t see this overloaded method in Apple’s docs for v2.2 of the SDK - is this an undocumented API call?

Thanks, and keep up the good work!

In the snippet on this page:

sqlite3 *db;
int dbrc; // database return code
dbrc = sqlite3_open ([dbPath UTF8String], &db);
if (dbrc) {
NSLog (@“couldn’t open db:”);
return;
}

Where does the variable dbPath come from in this code?

Is it supposed to be dbFilePath?

If that’s the case, it would also help to know how the variable is conveyed from the App Delegate scope to the View scope.

“working with habits different than”

should be

“working with habits different from”

This is pretty picky, but… the last paragraph of section 3.4 (Deleting rows) says that first you delete the row from the table view, then from the array, but the code actually does these steps in the opposite order.

It’s not clear, or at least it wasn’t to me, that the code to call addButtonWasPressed goes in the initWithCoder method. I think it breaks up the flow too much when the reader has to go consult the sample code just to understand what’s going on.

Second sentence- I think “collection of team” should be “collection of teams”.

This is a general comment, but the spot that brought it to mind is the last bit of section 3.9.

The method viewDidLoad is shown in its entirety, even though the part that the previous paragraph refers to is only the middle line. I had to think about it to figure that out, and IMHO there is enough to think about in the content of the book without having to also think about the layout of the book.

Mainly the problem is that it’s not consistent - sometimes just the new lines are shown, other times the whole method is. My personal preference would be to always show the whole method with the new lines highlighted somehow so they stand out, but consistency is more important than which style you choose.

You say “You should never do something with animation unless the
view that would be animated is the top most view.”. I agree, but I think the sentence needs a “, because…”. While it’s probably obvious to most readers, there are going to be some newbies who won’t get it.

The chapter multiple view controller is very hard to understand. The process to use IB appears like a sort of “wodoo” during the connection between the views and other elements.

Maybe more explanations are needed.

Regards
Andrea Fanfani

Maybe a little appendix with the basics of objective-c will be a great addendum

sqlite> insert into “shoppinglist” (item, price, groupid, dateadded)
…> values (“iPhone 3G”, “199”, 1, DATETIME ('NOW'));
…> go

should be:

sqlite> insert into “shoppinglist” (item, price, groupid, dateadded)
…> values (“iPhone 3G”, “199”, 1, DATETIME ('NOW'));
sqlite> go

You don’t give the code to the “self.states” method in both the StatesAppDelegate code snippets. Someone may try building and running the code only to find an unrecognized selector “states” exception.

In the last line of the paragraph immediately before the code for initWithCoder:, you have ,“… it doesn’t call or get called by other method in our view controller”. The word “method” should be plural.

In the last paragraph before section 3.5, second sentence, you have, “We need to delete the row from table view …”. You need to insert the word “the” before “table”.

The last sentence in the 2nd to last paragraph reads: The code for that controller
is again very similar to the controllers from the previous example so I
won’t got into any more detail here." It should be “…so I won’t go into any more detail here.”

In the last sentence on the page, you have, “… move it to the right edge it to fit …”. The word “it” after the word “edge” should be removed.

In the paragraph after the image of control-dragging a connection to the text field, you talk about bringing up the list of outlets for the File’s Owner and selecting the navigationItem outlet. I can bring up the list of outlets but I can’t select the navigationItem outlet. I am not sure why I would want to do that even if I could since normally I would control-drag a connection from File’s Owner to the Navigation Item and just select the correct outlet.

In the next paragraph you talk about verifying that the outlets have been set up properly by control-clicking on File’s Owner. You only mention 2 of the 3 outlets that have been set. You should probably also mention the navigationItem outlet to avoid confusion.

Please describe and show sample code for audio accessing, including sampling mic data and play audio through headset.
Please describe the audio drivers and library.

In the fourth paragraph, fourth sentence, you have, “… start scrolling off the top of bottom of the table, …”. The word “of” between “top” and “bottom” should be “or”.

The code in this example (demonstrating how to detect pinches) will lead to an NSRangeException in touchesMoved if run on a real device and one finger “escapes” off the screen during a pinch. It works fine in the simulator.

First few lines currently look like this:

- (void)touchesMoved:(NSSet )touches withEvent:(UIEvent)event {
if(YES == pinchZoom) {

Instead, I’d suggest this:

- (void)touchesMoved:(NSSet )touches withEvent:(UIEvent)event {
\tif(YES pinchZoom && event.allTouches.count 2) {

In the last sentence on the page, you have, “… and an design for …”. The word “an” should be “a”.

In the code for createNewTeamCellFromNib, shouldn’t you be using nil instead of NULL in all cases?

In the last sentence on the page, you have, “… show in Figure 3.1, …”. The word “show” should be “shown”.

The code for tableView:cellForRowAtIndexPath contains the code that was in there prior to changing the code for using a custom table view cell. It would be less confusing to use the newer code using the TeamCell class.

In the first paragraph of the section “Adding a button with Interface Builder”, fourth sentence, you have, “… setting a dynamic attributes like …”. Either the word “a” should be removed or the word “attributes” should be singular.

In the third paragraph, second sentence, you are missing a “(” before “Figure 5.3, on page 91)”.

In section 5.2, you should probably mention that you need to add an instance variable for states and make it a property of the class StatesAppDelegate. It will make the code more understandable.

At the bottom of the page, you refer to the Table Views chapter as being unwritten yet. Probably should remove that.

In the third paragraph where you talk about adding the TableView to the view for the ByPopulationViewController, you should probably tell the user to delete the label and text that is already in the view before adding the TableView.

‘expect’ should be ‘expected’

the user will be ‘expect’ to provide. (in the last sentence on this page.)

should be:

.. the user will be ‘expected’ to provide.

The paper book will be different, but for a PDF book, it’s almost like HTML when I can click from the TOC to a section called 6.5 Writing Data to Files.

Since that’s the case, you may want to avoid assuming such a linear conversational tone.

Example: "As you might have guessed, the stream-writing subclass of NSStream is NSOutputStream, and its essential method is write:maxLength:.

I just clicked straight to this section from the TOC because I’m interested in learning how to store (save) data and thought ‘Writing Data to Files’ would help with that.

I haven’t read the text leading up to this bit and wouldn’t have “GUESSED” anything.

The book has a very conversational tone - which while pleasant.. seems like it could be isolated from the ACTION ITEMS.

IDEA: any page that has Xcode or IB To Do items should be put in a completely separated part of the page. Like a recipe. So you could flip from page to page and just do the tasks. The commentary, insight, and conversation could happen above.

Parenthetical text can be distracting. This may only be to people who are auditory and hear the text as they read in their minds.

In the last paragraph on this page, you have three thoughts in parenthesis.

While we could continue in IB for a bit longer (using the same technique
we used in Section 2.1, Your First View Controller , on page 27 to infor m
IB of our intent to have an action method on the view controller) we will
instead jump over to Xcode and make the changes there (I war ned you
it would be a bit bumpy). The reasons for this are twofold, one so that
you can see firsthand the great way IB and Xcode are integrated (IB will
know about the changes as soon as we make them).

I love writing I only have to read once to understand. A paragraph like this.. that doesn’t even really forward my skills, is time wasting.

ALSO: shorter sentences are more digestible.

Sentences that cover 4+ lines can be edited for clarity:

While we could continue in IB for a bit longer (using the same technique
we used in Section 2.1, Your First View Controller , on page 27 to inform
IB of our intent to have an action method on the view controller) we will
instead jump over to Xcode and make the changes there (I warned you
it would be a bit bumpy).

That’s one sentence.

I’d rather read something like:

"At this point, we could continue in IB like we did with Your First View Controller, or jump over to Xcode. We are going to jump over to Xcode for two reasons: 1.) you’ll experience the tight integration between IB and Xcode, and 2.) you’ll get used to jumping between the two applications as iPhone developers use both tools simultaneously.

[You thought one editor was tedious enough. Now you have everybody giving their editorial opinion.]

A great example of very tight, clear language is found in Twyla Tharp’s book: The Creative Habit

In the paragraph starting with: "The @class…

Right in the middle, you mention header includes (in parenthesis) while discussing ‘forward declarations’

The very next sentence begins with ’They are very messy…

In the flow, it feels like ‘They’ is talking about the subject of the previous sentence - i.e. ‘forward declarations’. But you’re saying header includes are messy. I think remove the parenthesis or swap "Header includes in for ‘they’

e.g. Header includes are very messy and you should avoid them.

This text has lots of what seem to be run-on sentences. Where you put two complete thoughts together with a comma, ‘and’ or some other connector.

E.g.

They are very messy and you should avoid them, use the forward declaration
in your headers instead of including the other header.

These are two complete sentences connected with a comma after …should avoid them,

[Found in the paragraph that begins with “The @class compiler”]

Throughout the book, all quotes are used incorrectly. When using LaTeX (as I expect you are) use the delimeters ` and ’ for single quotes and `` and ’’ (which is 2 apostrophes) to for double quotes. That way the quotation marks are the correct way round.

Example:
This is the `correct’ way of doing things.
``OK’’ he said.

This sentence is inaccurate:

In the implementation class, TeamCell.h, all you need to do is to syn- thesize these properties at the top of the implementation block, and to
release them in dealloc, as usual.

sqlite3 stores strings as UTF-8 (or UTF-16, if that’s what you supply… see the “SQLite Version 3 Overview” doc), so for retrieving values, initWithUTF8String: is more appropriate than initWithCString:. Thanks to reader Nickolay Nickolaev for reporting this in the forum.

First paragraph, type: If you
are providing more granular infor mation like how far your use rode her
bike then the location updates can be more like 100 meters. should be If you
are providing more granular infor mation like how far your user rode her
bike then the location updates can be more like 100 meters.

The book says icon.png must be added to Settings.bundle, but it does not say how that is accomplished

In the code excerpt where you set the DirectoryViewController’s directoryPath, you implicitly use an instance variable named directoryViewController without mentioning that it is the application delegate’s navigation controller’s top view controller after the application launches. Further explanation about this would be helpful.

In the last chapter: “A workable strategy” sounds not like this would be the apropriate way. I was surprised that this strategy was used.

Designing a Custom Table Cell
The next thing we’ll do is to design a cell in IB, and to make that cell
an instance of the TeamCell class we just defined. Begin by clicking
on “Classes” in Groups & Files and choosing File->New File. This time,
you’ll choose Xcode’s “Empty XIB” template and call the file TeamCell.xib.

Shouldn’t that be “clicking on ”Ressources“”

For clarity, rename this object from “Table View Cell” to “Team Cell”.

It took me a while to figure out that I can rename it unter Interface Builder Identity.

Up until chapter 5, you have been using a tutorial style where you walk the reader through creating all the code. This chapter seems to change to a mixture of tutorial and talking about code you provide. If this is intentional, you might want to put something at the beginning of the chapter that lets the reader know that you are changing your approach.

Just a suggestion.

On pp. 61, in “Designing a Custom Table Cell” the instructions say to create the TeamCell.xib in the “Classes” folder under Groups & Files, as opposed to under the Resources folder, where I’d expect.

“Begin by clicking on ”Classes" in Groups & Files and choosing File->New File. This time,
you’ll choose Xcode’s “Empty XIB” template and call the file TeamCell.xib. "

I think this is just an error, but if not then why this nib file goes into the Classes folder should be explained.

“back and fourth” -> “back and forth”

To get the By Area tab to work correctly, you need to disconnect the view in the area tab in IB so it then says Loaded From “ByAreaView.nib” otherwise the By Area tab displays the same view as the By Population tab. I didn’t see anything in the section explaining this.

In the last paragraph, first sentence, you have, “… the PreferenceSpecifiers array is dictionary …”. You should have the word “a” before “dictionary”.

In the second to last paragraph, last sentence, you have, “… method to return provide the UITableView …”. The word “return” should be removed.

Is correct the code in beta-8 with
[[self.states objectAtIndex:indexPath.row] name];

In beta 7 and in the source is “valueForKey:@”name“”

should be “by”

should be “need to do get our newly”

<photos is found the Contacts application.> should be "photos is found the Contacts application.

Instead of “- (void)viewWillAppear:(BOOL)flag” you should use “- (void)viewWillAppear:(BOOL)animated”. “flag” is nondescript, while “animated” tells you immediatly what the argument is for.

The “nonatomic” property seems unnecessary, and should probably be omitted, since it will only confuse a reader.

MainViewController.h*, create
IBOutlets for UILabels called timeLabel and timeZoneLabel.

First paragraph, third sentence: “In this chapter you will build custom user inter faces buy extend-
ing” -> “by extending”

Section 11.5, third paragraph: Second sentence seems to be the aftermath of a collision between two sentences. “context for you can then”

Last paragraph, first sentence: “setup” is not a verb. It should be “calculate or set up”.

Missing colon in method name:

“You can also supply an NSData as the contents argument to the NSFileManagercreateFileAtPath:contents:attributes: method above.”

(should be NSFileManager:createFileAtPath:contents:attributes:)

MainWindowController.h should be MainViewController.h

“In MainWindowController.h, create
IBOutlets for UILabels called timeLabel and timeZoneLabel.”

Cannot compile MultiTap sample code downloaded from site. Fails with 1 error. I am using latest code. SDK 2.2 with XCode 3.1.2

error is

Building target “MultiTap” of project “MultiTap” with configuration “Debug” — (1 error)
\t cd “/Users/neil/Documents/Projects/Scoreboard/iPhone SDK book/code/MultiTouch/MultiTap”
setenv PATH “/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin”
/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/gcc-4.0 -x objective-c -arch i386 -fmessage-length=0 -pipe -std=c99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -D__IPHONE_OS_VERSION_MIN_REQUIRED=20000 -isysroot /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator2.0.sdk -fvisibility=hidden -mmacosx-version-min=10.5 -gdwarf-2 -iquote “/Users/neil/Documents/Projects/Scoreboard/iPhone SDK book/code/MultiTouch/MultiTap/build/MultiTap.build/Debug-iphonesimulator/MultiTap.build/MultiTap-generated-files.hmap” “-I/Users/neil/Documents/Projects/Scoreboard/iPhone SDK book/code/MultiTouch/MultiTap/build/MultiTap.build/Debug-iphonesimulator/MultiTap.build/MultiTap-own-target-headers.hmap” “-I/Users/neil/Documents/Projects/Scoreboard/iPhone SDK book/code/MultiTouch/MultiTap/build/MultiTap.build/Debug-iphonesimulator/MultiTap.build/MultiTap-all-target-headers.hmap” -iquote “/Users/neil/Documents/Projects/Scoreboard/iPhone SDK book/code/MultiTouch/MultiTap/build/MultiTap.build/Debug-iphonesimulator/MultiTap.build/MultiTap-project-headers.hmap” “-F/Users/neil/Documents/Projects/Scoreboard/iPhone SDK book/code/MultiTouch/MultiTap/build/Debug-iphonesimulator” “-I/Users/neil/Documents/Projects/Scoreboard/iPhone SDK book/code/MultiTouch/MultiTap/build/Debug-iphonesimulator/include” “-I/Users/neil/Documents/Projects/Scoreboard/iPhone SDK book/code/MultiTouch/MultiTap/build/MultiTap.build/Debug-iphonesimulator/MultiTap.build/DerivedSources” -include /var/folders/uN/uN-y0p-QFj0gosJ5GyZPwU+TI/-Caches-/com.apple.Xcode.501/SharedPrecompiledHeaders/MultiTap_Prefix-hkxxgdvwcvnkvohkyohesplizltp/MultiTap_Prefix.pch -c “/Users/neil/Documents/Projects/Scoreboard/iPhone SDK book/code/MultiTouch/MultiTap/Classes/../MultiTapView.m” -o “/Users/neil/Documents/Projects/Scoreboard/iPhone SDK book/code/MultiTouch/MultiTap/build/MultiTap.build/Debug-iphonesimulator/MultiTap.build/Objects-normal/i386/MultiTapView.o”
i686-apple-darwin9-gcc-4.0.1: /Users/neil/Documents/Projects/Scoreboard/iPhone SDK book/code/MultiTouch/MultiTap/Classes/../MultiTapView.m: No such file or directory
i686-apple-darwin9-gcc-4.0.1: warning: ‘-x objective-c’ after last input file has no effect
i686-apple-darwin9-gcc-4.0.1: no input files
\t\ti686-apple-darwin9-gcc-4.0.1: no input files
\t\ti686-apple-darwin9-gcc-4.0.1: no input files
\t\ti686-apple-darwin9-gcc-4.0.1: no input files
\t\ti686-apple-darwin9-gcc-4.0.1: no input files
Build failed (1 error)

“The other thing to notice is how you can refer to a method by means of the @selector keyword, which gives you the selector type needed for the instanceMethodSignatureForSelector method.”

“instanceMethodSignatureForSelector” should be “methodSignatureForSelector”

I’ve trouble with creating a provising profile with the documentation Apple supplies. Especially with the Identifier (e.g. is it possible to use wildcards here or should I register every identifier beforehand?). My suggestion is to expand the section »1.5 Running your app on your iPhone« a bit more and cover Apples developer portal where I’ve to create the profile etc. too.

The code example from tableView:cellForRowAtIndexPath doesn’t include the changes made in section 3.12 “Designing Table Cells with Interface Builder,” so it breaks continuity for those going cover to cover. I would add createNewTeamCellFromNib etc.

I’m using IB v3.1.2 (677), and when I drag the Label into the view window, no guides appear to snap to as referenced at the end of the third paragraph on this page. Further, once I drop the label onto the view, the background changes to diagonal gray stripes (which I didn’t expect) and I am not able to move the label with the mouse. Its blue handles appear, but I can’t drag the label to reposition it.

I was pretty careful to follow the instructions in the PDF exactly, so I think the text should be more explicit about how this task (moving the label into the view) is to be performed.

Regarding the erratum I just entered: turns out the problem was that IB launched showing the View Controller window, not the Window window. The instructions should explicitly tell the reader to double-click the Window item in the MainWindow.xib window and use that as the target for the drag operation.

“Begin by clicking on ”Classes" in Groups & Files and choosing FileNew File. This time, you’ll choose Xcode’s “Empty XIB” template and call the file TeamCell.xib." surely this should be the Resources group not Classes?

The last paragraph should read:

“This is our first peek at pushViewController:animated: ” - the 5th word should be P-E-E-K.

The last sentence on the page reads: “So when you test your preference
handling, you’ll want to be sure to sure that you stay…” You have an extraneous “sure to” in there.

In the middle of the first paragraph, you say to use an NSNumberFormatter to format the date strings you get back from SQLite. It should be NSDateFormatter instead.

The last sentence on the page reads:

“The view controller uses this array in its tableView:cellForRowAtIndexPath:( ) method to return provide the UITableView…”

It should read:

“The view controller uses this array in its tableView:cellForRowAtIndexPath: method to provide the UITableView…”

In other words, remove the parentheses (since Objective-C methods don’t use them) and remove the word “return”.

I failed to follow your directions for connecting the button to buttonClicked: I’m not clear on what to hold and when to release.

I found the following to work for me: click File’s Owner, Apple+2 to get to the connections inspector, drag the nub next to buttonClicked: to the button, then select Touch Up Inside.

Your way seems like it’d be easier… except I don’t understand it.

Thanks!

In order for the Struts & Springs configuration referred to on P21 and illustrated on P22 to work, the Label needs to be set-up with text alignment centered, otherwise the label text sticks to the left side when the label is rotated

In the second code snippet on this page the if statement starts with:

if(nil != editorViewController.field.text &&…

This ‘reads’ (in my head) as “if nil is not equal to field’s text contents and…”.

I’d suggest reversing this clause to be:

if(editorViewController.field.text != nil &&…

So it then ‘reads’ as “if field’s text contents is not equal to nil and…”. That wording seems to flow better/be more readable (IMO).

“UIInterfaceOrientationLandscapeLeft, or UIInterfaceOrienta-
tionLandscapeLeft).” - should be “or UIInterfaceOrienta-
tionLandscapeRight”?

While working through the example on the SDK 3.1.2, I was unable to add a NavigationItem directly to the view as indicated by the text. The tool seems to require that a NavigationBar is in place first.

I noticed a couple of differences between your download code/snippet and the sample implementation of tableView:commitEditingStyle:forRowAtIndexPath: that I’m seeing generated by the iPhone 2.2 SDK.

I’m not certain if the sample implementation has changed with 2.2 or if you just made a couple of changes not listed in the paragraph following the snippet. Anyway, here’s the sample implementation I see with the 2.2 iPhone SDK;

// Override to support editing the table view.
- (void)tableView:(UITableView )tableView commitEditingStyle:(UITableViewCellEditingStyle)editingStyle forRowAtIndexPath:(NSIndexPath)indexPath {

if (editingStyle UITableViewCellEditingStyleDelete) { // Delete the row from the data source [tableView deleteRowsAtIndexPaths:[NSArray arrayWithObject:indexPath] withRowAnimation:YES]; } else if (editingStyle UITableViewCellEditingStyleInsert) {
// Create a new instance of the appropriate class, insert it into the array, and add a new row to the table view
}
}

The unmentioned differences I picked out are;
1. [tableView deleteRowsAtIndexPaths:withRowAnimation:] is passed YES instead of UITableViewRowAnimationFade in the 2.2 sample
2. if (editingStyle == UITableViewCellEditingStyleInsert) is ‘else if’ in the 2.2 sample

Somewhere between page 55 and page 58 the declaration of addButtonWasPressed in RootViewController.m has changed from:

- (void)addButtonWasPressed…

to:

- (IBAction)addButtonWasPressed…

Syntactically I believe they’re essentially the same (since the .h declaration is already flagging this as an action for IB’s benefit) but I’d suggest that the .m declaration remains as one or the other return type throughout to save people wondering why it changed (or not noticing it changed). Especially since page 58 says “…then add the following code to addButtonWasPressed” (e.g. inside the existing (void) declaration set up on page 55).

Previous convention (pages 32 and 35/43) suggest that this should be IBAction in both .h and .m to remain consistent.

“Click the ”Team Cell" in the document window and go to the Identity Inspector (D4) and set the class to TeamCell."

You were already told to do this at the top of page 64.

Paragraph 1, underneath the inset, “use” is clearly the wrong word: “If you are providing more granular information like how far your use rode her bike…”.

In paragraph on we are instructed to add the Core Location framework to our project, but the location of the framework isn’t wrapped and thus impossible to discern.

“Longitude” is misspelled in Figure 15.1: Location Coordinates.

Latitude is also misspelled in Figure 15.1.

“ihpone-test-dir.conf would be a good choice.”

should be: iphone-test-dir.conf

" There are three ways to view the list of items, you can look at just the icons, which is the way most experienced …"

That’s multiple sentences. A period would help somewhere in there…

§5.2 perhaps too much familiarity is assumed with Cocoa data classes at this point. Without looking at companion source I’d little idea that the correct thing to do once constructing the data was to write self.states = [NSArray arrayWithArray:data];

At least a note saying that from here on you need to be using the companion source would be good.

“Once the zoom factor is calculate …”

should be: calculated

You omit to point out that both the class of the File’s Owner in the ByAreaView.xib AND the second tab controller view in MainWindowView.xib should be ByAreaView. Also you omit to say that the delegate outlet of the UITableView in ByAreaView.xib should be the File’s Owner.

(Disclaimer: I know little about Cocoa, but I seemed to need to do these things in order to get the example to work.)

“Don’t let he volume of code throw you off though.”

“he” should be “the”

Formatting the SQL statement with initWithFormat as shown leaves the application vulnerable to SQL injection attacks, and at the very least simple breakages such as quote characters in the shopping item name.

“…calculate the appropriate ratio to preserve
the aspect ratio (as seen on line ).”

missing line number

The sample code (in the book and downloadable archive) specifies a “normal” alpha value (1.0) with a blend mode of kCGBlendModeDifference whereas the text refers to the code specifying a different alpha (0.75) and a normal blend mode (kCGBlendModeNormal).

“our code responds buy bringing up the image picker.”

“buy” should be “by”

There’s currently no coverage of UISeachBar. Would dovetail nicely with the sqlite chapter methinks.

“This code will set the duration of any animation for the view wether or not…”

wether should be whether

Page 35 in the source code snippet incorrectly states

@class EditorViewController;

rather than StartViewController

“Even when two towers are in range the numbers can be of f buy quite a bit.”

“buy” should be “by”

Here’s a simpler of coding the TeamCell-finding loop:

\tNSObject* nibItem;
\twhile (!(nibItem = [nibEnumerator nextObject])) {
\t\tif ([nibItem isKindOfClass:[TeamCell class]])
\t\t\treturn (TeamCell*)nibItem;
\t}
\treturn nil;

“The table in the upper portion of the window show the search results.”

“show” should be “shows” or there’s a missing “will” etc.

Can we have a chapter on testing please? I looked this up in the forums, and getting unit tests for the iPhone seems rather non-trivial.

Given that this is a Pragmatic book, it feels really wrong that testing isn’t covered.

Thanks!

I am trying very hard to make the example in chapter 2 work, and am giving up with almost no understanding of how a modal view controller works, or any real idea of where to look for that information.
I admit I am somewhat new to Cocoa dev and Iphone which is why I purchased this book to use it as a framework to dig into the whole process.
I think when I started it was more of an Alpha not a Beta and now at B8.0 I think the early sections require a lot of work, lots of question marks referring to other sources of information etc.
I also think chapter 2 is broken unless you already know how to finish the task itself, the addition of the view controller is not clear specifically the following:
“For the final step, connect the editorViewController
outlet of the File’s Owner object to the new view controller. To do
that, control click on the File’s Owner and drag to the new view controller.
When you let up on the mouse a pop-up window will list the
editorViewController outlet, select it.”
I don’t get anything like this when I try that operation and I have recreated the project at least twice because I would like to understand this whole concept because it is important…..
I give up, and reluctantly move forward hoping to have a better experience.

So, after a chapter dealing US basketball teams, we’re now working with US states? Couldn’t this be a little less US-centric?

In the code sample starting on page 127 and continuing on page 128 (with a link to the full sample [FileIO/FlippingPreferableClock/Classes/MainViewController.m] on page 127) the variable clockViewUpdateTimer is never declared.

In my own code, I can declare it as an NSTimer *, but then I get a warning saying that the variable is never used. What is the purpose of that line in the sample?

The sample code should just make sense, and if it doesn’t appear to, such instances should be explained.

Sorry I typed enter too soon earlier. This is code that does exactly what the old one did:

\tNSObject* nibItem;
\twhile ((nibItem = [nibEnumerator nextObject])) {
\t\tif (![nibItem isKindOfClass:[TeamCell class]])
\t\t\tcontinue;
\t\tTeamCell* teamCell = (TeamCell*)nibItem;
\t\tif ([teamCell.reuseIdentifier isEqualToString: @“Team”])
\t\t\treturn teamCell;
\t}
\treturn nil;

Regarding the stuff under “the back button” — we have already implemented this in section 3.8 pages 58/59. It would’ve been nice to have all this explanation then, or at the very least have a forward reference there.

Thanks!

How about making the + button add a random team. This would eliminate the need for a 2nd view. The point is chapter 3 would actually be about table views, and then chapter 4 would introduce having multiple views and navigating between them.

Thanks!

Five of the nine occurrences of “the users” in this PDF should actually be “the user’s” (possessive). These five occurrences are on pages 33, 179 (two), 207, and 233.

sec.deletingRows looks like it’s section 3.4 Deleting Rows?

It seems to me that the companion source for this leaks the mutable array. I think -createData should have a [data release]; after the line with self.states = …

Thanks for the book.

At the bottom of this page (and in your gray box up top) you say “For more details on both the property and protocols of Objective-C see the Apple docs [?]”. You were probably already planning on doing this but I would recommend pointing readers to Apple’s “The Objective-C 2.0 Programming Language” guide. It should provide the reader all the details they need to know about properties and protocols in the “Declared Properties” and “Protocols” section. HTH

In the first paragraph below the viewDidLoad code sample, you say that blue layer’s zPosition is 100, when the code sample says it’s 5. Also the paragraph says the red layer’s zPosition is 0 when the code sample says it’s –5.

Creating A Custom Table Cell Class

text reads:
So, in your Groups & Files, click on the “Resources” folder and select
File->New File. This time, the template you want is the “UITableViewCell
subclass”.

Should this be the Classes folder?

“Our AddTeamViewController view needs a title and a button to get back to
the list of teams. Search for “Navigation Item” in the Interface Builder
library. Drag an instance into our AddTeamViewController document win-
dow. Then set the title of the Navigation Item to “Add Team” in the
attribute inspector.”

I think this needs a little clarification/cleanup. The way I read this paragraph it seems to suggest that the Navigation Item you’re adding is setting up both the ‘Teams’ button and the view title. Yes, it’s setting the title for the view but it doesn’t add the button. You can omit adding the navigation item to this view completely and, although the AddTeamViewController view will then be untitled, you’ll still get the navigation item.

I believe the ‘Teams’ item comes from MainWindow.xib -> Navigation Controller -> Root View Controller (Teams) -> Navigation Item (Teams).

If there was a third view called by AddTeamViewController then, I believe, the ‘Add Teams’ Navigation Item added comes into play (to display the navigation item that returns from the third view to the 2nd).

In the second paragraph below the picture, it says to provide IBOutlets for the 2 labels so that we can update their text values with the latitude and longitude values. The outlets should be for the text fields not the labels.

The second paragraph (outside of the “Joe Asks” box) says to open the HelloViewController.xib by double clicking on it. However, it doesn’t say where to find that file. I found it under the Resources folder, but it seems like it might be useful to suggest to people where to find it.

I’d also hyphenate “double clicking” but I don’t know that it’s vital. :)

The book states that the shouldAutorotateToInterfaceOrientation method will be commented out, but in my version of Xcode and the SDK (Xcode 3.1, not sure how to check my iPhone SDK version if possible), the function looks like so (between the dashed lines):
———————————
- (BOOL)shouldAutorotateToInterfaceOrientation:(UIInterfaceOrientation)interfaceOrientation {
\t// Return YES for supported orientations
\treturn (interfaceOrientation == UIInterfaceOrientationPortrait);
}
———————————

No comments whatsoever.

The paragraph:
“Next we add the text field that the user will type into. From the Library
drag out a text field onto the view. Place it wherever you see fit. Then
connect the field outlet from the files owner to the newly placed UITextField.”

That last instruction to connect the field outlet from the file’s owner to the newly placed field wasn’t exactly clear. I’d say something like “Then, using a control-click on File’s Owner, drag up and connect the field outlet to the newly placed UITextField.” or something similar. If nothing else, the word “files” needs an apostrophe.

In the discussion of accelerometer update frequency, it says the following:
“…you generally want to run closer to frame rate, so an interval of 0.33 (30 updates per second) or even 0.2 (50 updates per second) is appropriate”

The 0.33 and 0.2 are an order of magnitude off, aren’t they? I believe those would be 3 and 5 updates per second, with it actually wanting 0.03 or 0.033 for 30 FPS and 0.02 for 50 FPS.

This whole sample doesn’t work if the clock is set to 24-hours in the System Setting. Verified on both iPhone OS 2.1 and 2.2.

“fourth” should be “forth” in the sentence:

You will be switching back and fourth between pushing the applications we build to your iPhone and the simulator often.

Don’t forget to #import “PlayersTableViewController.h” at the top of RootViewController.m to be able to run the code in section 4.6.

“Applying this changes the source files, but not the RootViewController.xib file that contains the view.”

It isn’t clear here that we’re talking about the source files filenames. It’s not quite correct to say that the RootViewController.xib hasn’t been changed, as it has, just not it’s filename.

You can eliminate the endOfStreamReached variable by using a while (1) and break statements.

On pp. 63 the instructions say to create the TeamCell subclass in the “Resources” folder: “So, in your Groups & Files, click on the ”Resources" folder and select File->New File. This time, the template you want is the “UITableViewCell subclass”. Call the class TeamCell." That can’t be right.

at the top of the page “then open the view by double clicking on it. Add a table view and …”

Following this led me to a situation where I had the table view contained in the original view. When I picked the By Area tab, the app blew up with an exception which I finally figured out by looking at the console:

2009-01-03 21:49:08.141 States[20087:20b] * Terminating app due to uncaught exception ‘NSInternalInconsistencyException’, reason: ‘-[UITableViewController loadView] loaded the “ByAreaView” nib but didn’t get a UITableView.’

I deleted the original view in the xib, then added JUST the UITableView and connected its data source to the file’s owner, and the app worked!

NSDictionary doesn’t respond to name, andrea fanfani is right,

cell.text = [[self.states objectAtIndex: indexPath.row] name];

needs to be:

cell.text = [[self.states objectAtIndex: indexPath.row] objectForKey: @“name”];

“Even when two towers are in range the numbers can be off buy quite a bit.”

The “Exploring Directories” section on this page isn’t clear - are you are discussing the design of the application that will be created in the following pages, do you expect the reader to create the application at that point or do you expect the user to download and view the sample program. (personally I agree with the first errata posting about “… a drastic turn at this point…”)

Section 4.3, second paragraph
Please replace “then pop it onto” with “then push it onto”.

Having code excerpts which don’t even indicate which method they are implementing, like the one on this page under “Getting File Attributes” makes following the discussion almost impossible, for me at least.

I think that there is a memory leak in the stream:handleEvent: method.

bufferString seems to be being allocated but never released.

Rather than assuming that enums will start with 0, it would be safer (and more readable) to assign the enum a value:

typedef enum {
PlayerPositionGuards=0,
PlayerPositionForwards=1,
PlayerPositionCenter=2
} PlayerPosition;

Suggest you throw an exception for the unexpected “default” case of both switch statements. Right now they just return –1, which could make for difficult debugging later.

Perhaps:

default:
throw [NSException exceptionWithName:“InvalidCaseException” reason:[NSString stringWithFormat:"Invalid case: %", section] userInfo:nil];

“since it doesn’t call or get called by other method in our view controller”

should be “…get called by any other method…”

Run-on sentence that should be split into two sentences:

The two view controllers that we are going to build have essentially the same code they differ only by the method used to get the list of states they display.

The following sentence is missing a period:

You should have something that looks like Figure 5.2, on
the previous page

Run-on sentence:

Congratulations you have been through all the view controllers that come with Cocoa Touch.

In the last paragraph on page 20 where you say to ‘save your changes and hit the Build and Go button’, it would be clearer for a beginner if you said something like ‘save your changes to the nib file in interface builder, switch to x-code, and then hit the Build and Go button’.

I think that it’s important to make it clear that they are two separate applications to somebody new to x-code.

CGFloat lowPassFilteredX = (acceleration.x * kFilteringFactor) +
(filteredAccelX * (1.0 - kFilteringFactor));
is undeclared - should this be acceleration.x?

This line of code does not work:

// populate the first view
directoryViewController.directoryPath = NSHomeDirectory();

unless you declare a DirectoryViewController field & property in FilesystemExplorerAppDelegate.h, synthesize it in FilesystemExplorerAppDelegate.m, and connect it in IB.

Use gender-neutral language: e.g. instead of “… when the user has indicated that he is done editing the text.” better use “… when the user has indicated that they are done editing the text.” (BTW I’m working through the book and finding it very useful)

cell.text = [[self.states objectAtIndex:indexPath.row] name];
should be
cell.text = [[self.states objectAtIndex:indexPath.row] objectForKey:@“name”];

The code sample implements an Aspect Fit, not an Aspect Fill as stated.

In the code snippet, you have IBOutlet on the iVars.

This will work, of course. But it is probably more correct to have the IBOutlet declaration on the properties themselves so that they behave correctly and use the retain or copy declarations of the properties, like:

@property (nonatomic, retain) IBOutlet UILabel* nameLabel;

Apple’s latest code samples are set up this way.

This code sample uses NSEnumerator. Since Objective-C 2.0 is required for iPhone development, one can use the new for loop to enumerate through the nib content NSArray.

Also, is there any reason that NSObject* is used instead of id? (I know that they’re the same thing).

The example can be rewritten as:

- (TeamCell*) createNewTeamCellFromNib {
NSArray* nibContents = [[NSBundle mainBundle]
loadNibNamed:@“TeamCell” owner:self options:nil];
TeamCell* teamCell = nil;

for (id nibItem in nibContents) {
if ( [nibItem isKindOfClass: [TeamCell class]]) {
teamCell = (TeamCell*) nibItem;
if ([teamCell.reuseIdentifier isEqualToString: @“Team”])
break; // we have a winner
else
teamCell = nil;
}
}
return teamCell;
}

Perhaps mention that a declaration: - (TeamCell*) createNewTeamCellFromNib; should be added to RootViewController.h

In the code in 3.10, add an if-clause to control for empty entries being created if nothing is typed:
if (textField.text != nil && [textField.text length] > 0 ) {
\t[rootViewController addTeamNamed:textField.text];
}

(The if condition is taken from p.43 but incorporates suggestion to simplify syntax by Liam Jones)

CH6.4 (… Deleting) - Error running under Sim OS 2.2

I seem to have stumbled on an incompatibility with the supplied deleteSelected: method code in the DirectoryViewController implementation.

All works fine in Simulator OS 2.1, but Simulator OS 2.2 gives the following…


.
.
.
2009-01-04 23:02:55.427 FilesystemExplorer[8689:20b] can delete file /Users/rob/Library/Application Support/iPhone Simulator/User/Applications/ED6A778E-C8CC-4A5C-80F8-A6FF602F702D/Documents
2009-01-04 23:02:55.429 FilesystemExplorer[8689:20b] deleting paths (
<NSIndexPath 0x542dc0> 2 indexes [0, 0]
)
2009-01-04 23:02:55.429 FilesystemExplorer[8689:20b] * Assertion failure in -[UITableView _endCellAnimations], /SourceCache/UIKit/UIKit-747.36.52/UITableView.m:679
2009-01-04 23:02:55.430 FilesystemExplorer[8689:20b] * Terminating app due to uncaught exception ‘NSInternalInconsistencyException’, reason: ‘Invalid update: invalid number of rows in section 0. The number of rows contained in an existing section after the update must be equal to the number of rows contained in that section before the update, plus or minus the number of rows added or removed from that section.’
.
.
.


Not managed to check on the iPhone itself so I don’t know if this is an OS 2.2 problem, or Simulator OS 2.2 problem.

When you say that the iPhone SDK doesn’t have support for unit tests, I think it would be helpful to mention the work-around developed by Google.

I can’t paste links here, so google-search “iphone unit tests”. The first result should be GTM (Google Toolbox for Mac), which has a wiki page named “iPhoneUnitTesting.”

I’m using this in my project, and it works. It doesn’t “just work”… but at least I can sleep at night.

I filed a bug in radar asking for seamless unit testing, and it got marked as a dupe. Maybe if enough people bug them…

I think you should recommend “scan-build xcodebuild clean build” instead of “scan-build xcodebuild”

I find this approach much more useful when I’m iteratively fixing the bugs that clang discovers.

Thank you for covering this tool! I wouldn’t have found it by myself, and it rocked my build!

In the last paragraph of 4.4, for clarity, change “… go set File’s Owner to be PlayersTableViewController.” to "… go (to the Attributes inspector and) set File’s Owner’s Class to be PlayersTableViewController.

In the 1st para it says: “To make the delete button work you just have to implement a few lines of code in your Table View Controller and you’re done.” It would be good here to see what those few lines of code are. I’ve deleted the IB steps and implemented: self.navigationItem.rightBarButtonItem = self.editButtonItem; in PlayersTableViewController.m and it all works fine. What would I have to code to get it all working if I were to go down the IB route?

FilesystemExplorer violates Apple’s UI guidelines for the iPhone by maintaining selection state. Tapping a row should have an immediate action, rather than maintaining highlight and waiting for the “edit” button to be selected in anticipation of a delete. cf. blogs.oreilly.com/iphone/2009/01/thinking-about-table-selection.html for more. Should use row-swipe to delete, then save “edit” button for add file or directory.

Hi Bill,

In -createNewTeamCellFromNib you iterate over the top-level objects of the nib file. Although this works, Apple recommends using IBOutlets to access objects in nib. In such a case I would connect the IBOutlet from the nib file’s owner and in -createNewTeamCellFromNib call -loadNibNamed:owner:options, the connection will be made and you can return the connected object.

You can then also raise an exception if the reuse identifier isn’t set, this is a programmer error that would never allow cells to be dequeued from the table.

Jon

Line #28 of drawRect is a duplicate in BarGraphView.m

ABRecordSetValue(person, kABPersonFirstNameProperty,
(CFStringRef)"Wonder", &error); should be ABRecordSetValue(person, kABPersonFirstNameProperty, (CFStringRef)“Wonder”, &error);

The Joe Asks box makes a reference to the ‘unwritten’ media play back chapter but the chapter (ch14) is already included in this verson

Core Services lists “location awareness” twice.

Near the bottom of the page, where it says “So, open SayHelloViewController.m”, I believe that it should say “So, open HelloUserViewController.m”

Where it says, “With the project
opened in Xcode, you should have a window like the (as yet) unwritten
fig.helloiphone.helloproj.”, I believe that this should be replaced with a link to the helloiphone project as it is already written.

for the life of me, I keep getting an error when I type in this code

-(void) sayHello: (id) sender {
\tNSString* userName = [self nameField].text;
\tNSString* helloMessage = [[NSString alloc] initWithFormat: "Hello %", userName];
\t[self helloLabel].text = helloMessage;
\t[helloMessage release];
}

on the top of the page.

Repeated word “where” in last sentence in first paragraph.
"Like C, you also need to indicate where where the com-
piler can find other code you’re using, by importing the header file of
classes you refer to in your headers or implementation.

Bullet point says “we get the label with [self helloLabel] and then get the text
that’s been typed into it.” Text is from nameField, not helloLabel. Also, ivar can be referenced as just “nameField” sted self.nameField or [self nameField].

Last sentence. “a small, lightweight runtime to the runtime objects.” delete the beginning “a” to read “small, lightweight runtime to the runtime objects.”

The second to last paragraph reads “…it uses the
interface header to declared that...". It should read "...it uses the interface header to declare that…”

middle of page: First lets look at the edit code.
should read: First let’s look at the edit code.

Bottom of page:
reads: If so then the view controller loads that nib file passing it’s self in as the File’s Owner.
should read (I think): If so then the view controller loads that nib file passing self in as the File’s Owner.
Also “self” should probably be in a different type face.

“…we’ll pass a reference to the current instance
of the RootViewController to the AddTeamViewController setting it as its
delegate.”
A bit of pronoun confusion here, where the text reads “it as its”, it is difficult to know which controller is the delegate of the other. Specificity is a good thing.

section 2.5 begins with…

“The application delegate is an example of one of Cocoa’s most signifi-
cant design design patter ns: delegation. ”

(double “design”)

Missing period on first bullet point: “later in the chapter”

Per users above, I received “error: request for member ‘text’ in something not a structure or union” using the bracket self syntax. This worked however:

- (void) sayHello: (id) sender {
\tNSString* userName = nameField.text;
\tNSString* helloMessage =
\t[[NSString alloc] initWithFormat: "Hello %", userName];
\thelloLabel.text = helloMessage;
\t[helloMessage release];
}

I am having difficulty with the sqlite section. There seems to be a star identifier used in the select commands, I cannot find this character and cannot seem to find a work around. If you could mention how to create that star character you use it would help those of us who do not know how to find it. -Thanks, JT.

The code to dismiss the keyboard at the bottom of sayHello should be:
[nameField resignFirstResponder];

pp36, code line 2 yields

HelloUserViewController.m:14: warning: ‘HelloUserViewController’ may not respond to ‘-nameField’
HelloUserViewController.m:14: (Messages without a matching method signature will be assumed to return ‘id’ and accept ‘…’ as arguments.)
HelloUserViewController.m:14: error: request for member ‘text’ in something not a structure or union

pp36, code line 5 yields

HelloUserViewController.m:17: warning: ‘HelloUserViewController’ may not respond to ‘-helloLabel’
HelloUserViewController.m:17: error: request for member ‘text’ in something not a structure or union

switching the contents of the header to look like so works, but this is cargo-culted from a later example and I don’t really understand what’s going on:

#import <UIKit/UIKit.h>

@interface HelloUserViewController : UIViewController {
\tUILabel *helloLabel;
\tUITextField *nameField;
}

- (IBAction) sayHello: (id) sender;

property (nonatomic, retain) IBOutlet UILabel *helloLabel; property (nonatomic, retain) IBOutlet UITextField *nameField;

@end

… you must also add @synthesize to the implementation:

synthesize helloLabel; synthesize nameField;

In the last sentence before the bullet points start, “can” is repeated:

“…you can can examine the parts…”

It’s unclear at what point in the text the diagram comes in. Is it part of the last paragraph at the bottom of 38 or the first paragraph on 39. It seems to float without any direct connection and currently adds little value. It should be tied in better.

Assuming the diagram on 39 is describing the setup from the bottom paragraph of 38, it would be better to explain which one is the window, which is the app delegate, etc. Or maybe (for those of us new to XCode) just explain all the icons in the screenshot in one go.

This summary is confusing at best. I feel like you are teaching me how laces are tied. Would an annotated class diagram/other diagram help? Maybe have thought bubbles that provide interesting detail (like object x loads from a different xib) overlay the diagram.

“affect” not “effect” in “that effect the whole application occur”

amiphd-b9_0.pdf, page 208:

“These kinds of functions are called convenience functions because that make some of our drawing easier.”

it says “we’ll be able style” - I presume it means to say, “we’ll be able to style.”

in the last paragraph:
“the string (an nobody can be, ”
‘an’ should read ‘and’
ie:
“the string (and nobody can be, ”

Penultimate paragraph:

“but instead of describing how an existing class’
methods work, it describes when”

“methods work” should be “method works”

3rd paragraph, 2nd bullet:
“Create a new nib file that will hole the UI for our new table view
controller”

hole -> hold?

RootViewController.h source:
Shouldn’t the DVDCabinetController be declared as an IBOutlet like it is in the @property signature two line below?

Unless there is a pressing need to save the half page of space it would take, I would strongly recommend you list the code added to tableView:numberOfRowsInSection: and tableView:cellForRowAtIndexPath: - it just makes following along easier and not dependent on immediate access to the website.

Also, you might mention setting the title to “Cases” in viewDidLoad

[self nameField] and [self helloLabel] don’t seem to work, no getter is defined (or synthesized).

>There are two new concepts here, first is the declaration that our class conforms to the UITextFieldDelegate protocol.

Actually protocols were introduced earlier as was UITextFieldDelegate. (P41)

>Control-Clickong on the File’s Owner and dragging to the text field.

Clickong

“we imagine you can figure this out” - This seems completely wrong in this book, and particularly in this chapter. After meticulously explaining the various steps, throwing this in there with no instructions, no reference, no hint, etc., is frustrating. People are reading this book to learn, being told they “should be able to figure this out” is off-putting.

Attributes Inspector is Command 6 not Command 1

Last paragraph:
“The only new bit here is the use of the method valueForKey:.”

Perhaps this should read “objectForKey:”? The code uses objectForKey and we used valueForKey back in Chapter 5.

As a side note, this is more of an Objective-C thing, but you might want to elaborate on the difference between objectForKey: and valueForKey: and when it makes a difference whether to use one or the other.

“Error” might not be the correct word for this but it’s an inconsistency. In the “viewDidLoad” method, the first line shown is “[super viewDidLoad]”. But this line was not part of the default code from Xcode. Then on page 72 we add another line to this method and the initial ‘super’ line is gone.

I think either it should be kept in both places (pp 70 and 72) or removed from both places.

Code does not compile for the HelloUser Project. I’ve made changes that do compile on my configuration of XCode but they are commented out below.

- (void) sayHello: (id) sender {
\t
NSString* userName = [self nameField].text;
\t// NSString* userName = nameField.text; //This Works
\tNSString* helloMessage = [[NSString alloc] initWithFormat: "Hello there %", userName];
\t[self helloLabel].text = helloMessage;
\t// helloLabel.text = helloMessage; //This Works
\t[helloMessage release];

“Hold down the ^ key and click on the button. Keep the ^ key down and drag toward the File’s Owner object.”

Is the ‘^’ key supposed to be the “Ctrl” key? This is confusing. Later in the chapter you refer to the “Ctrl” click, or right-click with a 2 button mouse, and I’m able to achieve what you intended. However, I interpreted this as hold down the UP arrow key and click, all that did is move my button up. This is a bit confusing and should at least be consistent.

Oddly, when I cut and paste from the PDF in Preview, it interprets the printed “^” character as “C”.

In the First Hello user Example, The code will not compile.
Missing Stuff:
Header File:
Missed to mention the use of @property after defining
the variables in the header.

Source File:
Must use @synthesize to make there variables avaliable in the controller
thanx

In second to last para: “First lets…” -> “First let’s…” Missing apostrophe.

Under ‘Getting File Attributes’, the reference to the callback accessoryButtonTappedForRowWithIndexPath: could instead be written as:

tableView:accessoryButtonTappedForRowWithIndexPath:

>As you can see, the first part of this method is identical to the version you saw earlier, except for line 7…

Lines 4-5 are different as well, here we are creating a pointer to a TeamCell and casting the dequeued pointer to a TeamCell.

>Now we have to take action when an row in the table view is selected.

when a row

You might want to warn the user to save the HelloViewUserController.h file before opening Xbuilder. On my first runthrough, I couldn’t find the outlets for the File’s Owner on page 34. Then I figured out that I hadn’t saved my header file and then in IB I picked “Reload All Class Files”.

The code sample here references a property named cabinetController, that’s not defined in any of the earlier snippets.

This is very difficult to follow. It references “The code you can download” but doesn’t link to it. Without that base code (or just figuring out what it’s supposed to be yourself), the examples don’t work.

Care and Feeding of SQL info box, last sentence:
“…or you’er going to want to.”: you’er -> you’re

The indentation level is incorrect for the code under the “if” statement (lines 9-16) in the example.

5th paragraph, photo.jpg should be photo.png (Figure 13.1 shows photo.png and photo.png is in the current source)

When I run the apps from supplied code (both States & StatesMore), I get memory leaks showing up in Instruments. Changing tabs in the apps increases the occurrence of leaks (initially it’s NSIndexPath & GeneralBlock-16). I have drilled down to Extended Details in Instruments, and when I doubleClick main in the Stack Trace this is the highlighted line of code (in main.m):

int retVal = UIApplicationMain(argc, argv, nil, nil);

I can’t work out where the leaks are coming from.

NB: Question posted on Forum about this.

3rd paragraph: “…to allow the user to only choose one on of the saved photos…” - one on of?

Footnote has two periods at the end of the sentence.

There should be a space between UITextFieldDelegate and protocol in the third sentence of the second paragraph.

3rd para 5th bullet" ‘RootViewControler.xib’-> ‘RootViewController.xib’

It would be nice to describe how to dismiss the text field when the user taps inside the main view, but outside any control.

I have a nice solution in my blog — googling my name and the word “blog” should pop it up.

Doube word near the end of the page:
“you can can examine the parts of the project by type:”

Unless I’m misreading it, the first sentence under section 5.1 needs to either remove the word “how” or add what the “how” is, for example: “… on your iPhone works.”

You say:
‘We are drawing the image with 75% opacity just to show off some of the flexibility…’

in reference to the code:
[image drawInRect:imageRect blendMode:kCGBlendModeDifference alpha:1.0f];

—

Looks like you’re drawing it with 100% alpha, but with a Difference blendmode.

2nd para: “We can set other variables that effect how a path is stoked too” should be “…affect how a path is stroked…”

The paragraph on the bottom of the page mentions putting more than one cell design in a nib. It might be worth pointing out that each time one creates a cell using the loadNibNamed:owner:options: method, one will actually instantiate all objects archived in the nib. The logic in your createNewTeamCellFromNib: method will pick out the desired cell, but the others will still be created, unless I’m misunderstanding something about nib loading… in which case that’s something you might want to explain. If I’m correct, though, it might be most economical to keep a single cell design in a nib.

Why the indent in the code before [self.navigationController pushViewController:self.cabinetController ??

“deserialized”; is that a word? Actually, I know the word. It’s the sentence I’m having trouble with. Take out the second parenthetical remark and your good to go.

Your
application’s first chances to provide custom logic come in the lifecycle
methods associated with the app delegate (such as applicationDidFinish-
Launching:) and the view controller it loads (which gets callbacks like
initWithCoder: when it’s deserialized from the nib and viewDidLoad when
its view is deserialized), although in our application, we don’t need to
do anything until the button is tapped.

In the second paragraph, the second sentence has an “it’s” instead of an “its”. In the next sentence, I’d suggest replacing the comma after “responders” with a colon.

Another erroneous “it’s” in the first full sentence on the page.

In the last full sentence on the page, the text says that a previous example demonstrated clearing a view when a user double-taps, but there is no such example in the current text. Also, “tapped” is spelled “taped”.

Oddly, when I “Open the Editor.xib by double clicking on it.” it had the effect of opening the text version of the file in the text editor. Not sure this was intended, I opened the f ile using File Open in the Interface BUilder

Then
connect the field outlet from the File’s Owner to the newly placed UITextField
by Control-Clickong

should be “Control Clicking”

You say “Next we need to connect the text field’s delegate up to the view controller
object”, do you mean the editor view controller or the starter view controller?

The sayHello: method is not visibly improved by use of properties, as the view controller accesses helloLabel and nameField as instance variables, not properties. Should just tone down the rhetoric here, or find a more useful application of the properties.

Hmm, this didn’t work for me. First, I have a compiler warning,
warning: no rule to process file ‘$(PROJECT_DIR)/Editor.xib’ of type sourcecode.xib for architecture i386
and second, I have terminating due to uncaught exception. The other examples before I reached this point all worked fine.

• Create a new nib file that will hole the UI for our new table view controller

— Believe it should be ‘hold the UI’

The code on this page doesnt compile. There is no type defined for dbFilePath.

In the third paragraph, last sentence, you are missing the word “this”. The sentence should read, “To accomplish this we need …”

preform, should be perform

cabinetController should be declared as IBOutlet for the next step to work.

You mentioning iterating over the results, but display that line of code. I understand you cant put every line of code in the book- but this is a pretty important line.

I could not find anywhere the details of the icon for the home screen. I would at least think somewhere in the book the dimensions would be mentioned if not how and where to set it.

The default XCode template includes [super viewDidLoad]; in the viewDidLoad method. I’m too much of a beginner to know if this should stay in or not, but I think it might be worth explaining why it needs to come out, if it does need to.

A prototype for - (TeamCell*) createNewTeamCellFromNib also needs to be added to RootViewController.h - unless you’re happy to put up with the warning. In which case, TabelCell.h needs to be imported in RootViewController.h

In the second paragraph, I think you mean click on the “Classes” folder rather than “Resources”

Hi -

I love the book, and have been using it a lot. I was working today, and had some horrible errors.

Specifically, I was using TabBars to switch between my application’s Views. Not only do you have to specify the NIB file for each tab in the TabBar, but also the UIViewController sub-class that is associated with it. This is NOT obvious in the slightest. If you leave out the class, either nothing happens and your class methods aren’t called, or you get a lovely crash with the error:

2009-02-08 23:22:59.697 Space02[11792:20b] * Terminating app due to uncaught exception ’NSInvalidArgumentException’, reason: ’* -[SourceCell nameLabel]: unrecognized selector sent to instance 0x5ed180’

Hmm. Thank goodness for Google, that’s all I can say :-)
The answer cropped in on the Apple support forum, here:

discussions.apple.com/thread.jspa?messageID=8550459

It would be VERY helpful if the book mentioned this. It’s tripped up a few people, and is very hard to debug.

thanks, and keep up the good work!

John

Having read chapters 2, 3 & 4, I feel that chapter 3 is in need of either a rewrite or being dropped altogether. It’s not written in a consistent tone to the surrounding chapters (which are much better written in my view) and it goes over ground that’s already or yet to be covered but in a much less clear way.

It’s patronizing too: “You’ve done it.” on page 52, paragraph 2 is an example of that.

In the first paragraph of 5.6 you mention that “in a more sophisticated application …” and then repeat that on the next page in paragraph 2. Perhaps these should be amalgamated?

In the final paragraph on this page you say that “The only new bit here is
the use of the method valueForKey:” except that there is no use of valueForKey on this page as far as I can see. There is a use of objectForKey though. I’m not sure whether the text or the code is wrong here.

longitude/latitude are wrong written on the image

In the begining of section 4.6, creating the view from Interface Builder is inconsistent with directions before and after this section where new views are created in Xcode. While it may be helpful to show that you can do it from either tool, at this point in the book is would be clearer to be consistent and use a “best practice”.

The first sentence of section 5.1 is not a complete sentence:

“The best way to get a feel for what you can do with a navigation controller is to take a look at how Apple’s Mail app on your iPhone.”

The last paragraph on 55 says: “When you mouse up on the label you will have a list of Outlets choose label then save the IB file.” The list I see only contains “view” and not the “label” outlet. Also, that sentence seems to be two sentences joined together, making me wonder whether the sentence is just nonsense created as the result of intensive editing.

Nothing in the “Target Action Paradigm” box makes any sense to me. Perhaps a diagram would help here. How does the information in this box relate to the text on page 55? I honestly have no idea of what it is you’re trying to convey, but the grey box makes it seem to be important, and I am frustrated that I can’t understand it.

I think part of the reason I’m having trouble understanding this section is that the variable names are not meaningful. A UITextField named “field” does not help me to understand what’s going on when we switch to the IB and we’re having to look for “field” or “label” or other generic terms used as variable names. Even variables named “x” or “y” would be better because at least then they’d stand out a bit more.

Hi, I am not sure, but after checking it 2 times in the 3.2 Multiple View Controllers Section. You forgot to mention that you have to add also following line : #import “EditorViewController.h” in the StarterAppDelegeate.m file.
I hope I have not overread it.
Second, I also would mention the order of the #imports .. I had errors during Building the app.. it took me some time to figure out why .. it was just the order of the #import - statements

Isn’t there anything wrong with the DVDCase app (chapter 5)? The very first time you click on Home or Work and goes the cabinetController, nothing shows up. But when you go back do that again, everything works fine. I downloaded all headers, implementation and xib files to be sure but still no success.

Shouldn’t insertStatementNS be released at some point after the statement has been prepared?

NSString *insertStatementNS = [[NSString alloc] initWithFormat … ];
const char *insertStatement = [insertStatementNS UTF8String];
dbrc = sqlite3_prepare_v2(db,insertStatement,–1,&dbps,NULL];
dbrc = sqlite3_step(dbps);
[insertStatementNS release]; // add this line?

The StarterViewController class also needs to synthesize the editorViewController as well as the label in order not to crash.

StarterViewController.m should include this line:
@synthesize label,editorViewController;

And StarterViewController.h should declare two properties:
property (nonatomic,retain) UILabel *label; property (nonatomic,retain) EditorViewController *editorViewController;

I hope that this is the right correction as the Starter app would not run until I completed these elements.

Robert

“The MPMoviePlayerController provides of state changes and other events during playback.”

missing “notification” or similar

“Whatever container you use, your video codec must either
H.264…”

missing “be” or similar

It is misleading to state that the synthesized properties you add to the code have any impact on the second version of sayHello:(id). The method works perfectly fine without them, as you rely on the built-in getter and setter for UITextField and UIlabel respectively, rather than any property of the controller-class.

“• A label for ”00:00" time, in 12-point Helvetica. Its minimum value should be 0.0, its maximum, 1.0.
• A slider for the current time."

“Its minimum value…” apples to the slider, not the text label.

Bottom of the page: “However is the view is not set … ” The first “is” should be an “if.”

In the last paragraph on page 198, it refers to a ‘previous example’ section 11.2 that is supposed to cover tracking multi-tap events. Section 11.2 doesn’t refer to multi-tapping at all. The multi-tap section is missing. The source code download has examples called Draw and DrawMulti that demonstrates what is missing from the text.

“take action when an row in the table view is selected” should be “take action when a row in the table view is selected” unless there’s more to this a/an rule than I’ve been taught.

In the chapter on core animation you mention a couple times that you’re going to “go into more detail” about layers and explain the relationship between views and layers. It would be great if you included more information, and perhaps a diagram illustration the relationship between views and layers. My mental model of this aspect of the iphone is still hazy after reading this chapter.

Line 28 of the code on page 214 is redundant. The three lines above it have already added the [self pathInRect:one] to the ctx context.

The one line of code on line 28 achieves the same as the 3 lines from 25-27.

last paragraph before “Inserting rows”: the sample implementation doesn’t include the beginUpdates/endUpdates wrapper — and the app works ok (Simulator 2.2.1-Debug). Has this requirement changed, or perhaps the wrapper is important further down the line?

“In IB, let’s create a new interface…” Is it worth mentioning that you must select “Cocoa Touch” on the left before selecting “View” on the right? In my case, “Cocoa” was already selected, and there is an item called “View” there too.

teamTextField.returnKeyType = UIReturnKeyDone;

Is this the same as setting “Return Key” under “Text Input Traits” in IB? Is one technique better than the other?

Memory leak in sample code. I haven’t tracked down the source yet, but if you run the sample HelloUser app with instruements in “Leaks” mode you will notice that the following steps create a leaked string:

1) Click text area, type ‘foo’, hit return.
2) click Say Hello
3) click text area again, type ‘bar’, hit return

notice the memory leak.

While adding the accesoryType, should probably note that you need to make two rows in the table (one for home/work). It’s only obvious you need to do this after going through the entire chapter and finally looking at the source code.

Discussing the changes in EditViewController, it would be helpful to mention the import-statement before implementing the methods. Otherwise readers might be confounded by the compiler-errors generated by building the project.

“With a factor of 0.1, the low-pass filter will use give a 10% weight to the
new value and 90% to its previously-filtered value.”

You should remove the word ‘use’ from the above sentence.

“After we crate the dictionary”

The word create is misspelled.

“After that is all setup we add the multi-valued
property to our person object with the address property.”

The word ‘setup’ should be 2 words.

The Info.plist code to set the app’s icon is HTML encoded

Sentence fragment at beginning of last paragraph. Replace first period with a comma, and uncapitalize the first letter following (the “I” in “It”).

Add commas before the first “and” and the first “then” on the page.

In second line of second paragraph, “so that when ever the message”: change “when ever” to “whenever”.

In the paragraph before the bulleted list, eliminate the period (after “very simple or very complex”), and uncapitalize the next letter (beginning “Depending”).

Last sentence of the paragraph before the bulleted list: Change “somethings” to “some things”.

In the first bulleted item, change “is public API” to “is a public API”.

First full paragraph, end of third sentence: reference to documentation of mailto URL has not yet been filled in.

First full paragraph, end of third sentence: reference to documentation of mailto URL scheme has not yet been filled in.

In the paragraph “Creating an Audio Queue for Playback”, you reference the AudioQueueNewOutput for playback but although the AudioQueueNewOutput for recording, which is false. For recording, it should be AudioQueueNewInput.

Last line of first paragraph of 21.1: “ah” should be “at”.

End of penultimate paragraph of 2.1: Since the name of the URL scheme document has changed, I recommend dropping “iPhone” from “iPhone URL
Scheme Reference”. You might also consider recommending a search for the phrase contained in a title, rather than a full text search. There aren’t as many relevant hits, but the most relevant is obvious.

Delete the last period in the penultimate paragraph of 21.1.

Last paragraph: “ad-hock” should be “ad-hoc”, or even better an italicized “ad hoc”.

The word “setup” should be replaced by “set up” on pages 58, 74, 241, 347, 354, and 398. (Do a search of the PDF with Adobe Reader to find these.)

Second complete paragraph: Second sentence is a run-on. After “leave it out”, change the comma to a period and capitalize the first letter of “even”. Also, add a comma after “cool looking” (and maybe change “cool looking” into “cool-looking”).

Third full paragraph on the page, fourth sentence: Change “your self” to “yourself”.

Third full paragraph on this page, first sentence: change “ad-hock” to “ad-hoc”, or perhaps and italicized “ad hoc”.

First line on page “… when an row …” should be “… when a row …” [I know … very minor, but thought you’d like to know]

end of 3rd paragraph: “… create a new subclass …” I think you are reiterating the steps to build a new table view based UI, however at first reading this appears to be an instruction to the reader to actually go ahead and create another new .xib file, etc. perhaps changing to “creating …” would be a clearer.

4th paragraph, 3rd line: “events that effect the whole application” should be “events that affect…”

end of first paragraph: “… Set the NIB Name … to DVDCabinetController.xib” This doesn’t work, the NIB Name must be set to “DVDCabinetController” (i.e. w/o the extension).

Not clear enough that you want reader to create code here; also not clear elsewhere that you are NOW expecting reader to insert code for @synthesize, #import, etc. State somewhere clearly that you are now expecting the reader to know enough to create their own code to supplement the snippets in the chapter.

Based on what has come previously in the book, it is not at all obvious to me what this line of code does:

if (self = [super initWithCoder:coder])

Any chance for a bit of explanation on that? I can see that the idea of the method is to initialize the “teams” array, but don’t grok that bit.

Missing space after period - 3rd Paragraph, “Open your new … to ByAreaViewController.Next …”

3rd Paragraph starting: “Open your new xib …” There is NO ByAreaViewController in the new xib file, so “connect the ByAreaViewController’s view outlet to the table view.” isn’t making sense to me.

4th para: “Control-Clickong” should be “Control-clicking”

Second bullet down is: Create a new nib file that will hole the UI for our new table view
controller

‘hole’ should be ‘hold’ Loving the book!

Could you please define which Synthesizer application on the Mac you used to create the audio files…I want to do the same thing, but I can’t figure out which app you used to save the voice to a file.

BTW, I have downloaded and read just about every other book on iPhone development, and this is book is far-and-away the best I have read. Your approach is elegant and well thought out! I recommend this book to everyone who asks!

Adding buttonClicked in this manner to the File’s Owner class action will add the action to the ButtonViewController.xib. This is incorrect and the process will crash horibly with the warnings about not finding the UIKit in /System/Library/Frameworks. Try it. Upon inspecting after the build, I found that that the image on the top of page 52 had two actions. If I removed the buttonClicked action on the .xib file and left the ButtonViewController.h file, all worked. Please address this broken process as it just wasted me 3 hours pulling my hair out.

Last paragraph, right before section 12.3 starts (Paths): paragraph begins with ‘Congratulations you have…’ should be ‘Congratulations, you have…’

The last sentence in the page: “When we type something into
the field and clicked the Done button the new value is placed in the label on the first view and the second view is removed from the window.” should read ‘click’ instead of ‘clicked’, in order to match tense.

However is the view is not set then the view con-
troller checks to see if its nib file is set.
Correction:
However, if the view is not set then the view con-
troller checks to see if its nib file is set.

Diagram at top of page refers to “DVDController” but explanatory text below refers to “DVDCabinetController”

In the last paragraph, one of NSFileManager’s methods is described. The text quotes it as
fileExistsAtPath:isDirectory
and then goes on to describe the second parameter. Since it accepts two parameters, shouldn’t its selector have two colons? I believe it should be
fileExistsAtPath:isDirectory:

At least, this is what I would expect in SmallTalk. It is also how the documentation bundled with Xcode lists the method. Otherwise, it looks like a single parameter selector whose parameter is named “isDirectory.”

“For what it’s worth, if you only care about checking whether something exists at a given path, and don’t care whether it’s a directory or a file, you can simply pass NULL for isDirectory.”

This is not a great suggestion. There is a perfectly good method which only takes the single parameter, fileExistsAtPath:

I would hate to come across a code base one day that is littered with lines and lines of [NSFileManager fileExistsAtPath: path isDirectory: NULL]. All those extra characters! :(

The text refers to valueForKey: in the text at the end of the page — ‘The only new bit here is the use of the method valueForKey:.’ But the new selector in the code listing is objectForKey: — ‘cell.text = [[self.states objectAtIndex:indexPath.row] objectForKey:@“name”];’

“Next up we will start to see some of the lower level API’s to interact with the iPhones file system.”

Rather than “iPhones”, this should probably be the possesive “iPhone’s”.

“Next up we will start to see some of the lower level API’s to interact with the iPhone’s file system.”

3rd para: “To accomplish we need to…” should be “To accomplish this we need to…”

In the second to last paragraph on this page, “Choose the View Template” is a bit confusing. I assume that user should choose “Cocoa Touch” in the left menu first and choose “Cocoa Touch View Template”. There is also a “Cocoa View Template” if the user chooses Cocoa only in the left menu. See the confusion? I think it should be clearly pointed out that the user should choose “Cocoa Touch View Template” instead of just “View Template”.

Also, when saving this new view, IB takes the user to the documents folder. Maybe for someone it’d be beneficial to know that they should navigate to their BasketballTeams project folder and save it there.

It would be nice to explain here why we’re importing RootViewController.h in AddTeamViewController.H (header file) and just moments after we’re importing AddTeamViewController.h on top of RootViewController.M (implementation file, and not header file!)… This is a bit confusing. Some things we import into header files, others we import into implementation files. Why? :)

I think that layers are used for the first time in this PinchZoom example; as far as I can tell they are not explained at all in this example or prior to it. This makes the awakeFromNib method unexplained “magic”.
General comment: it is difficult as a reader to know when to create my own code and when to just load and use the code you provide. Seems to change a couple times within the book up to this point.

“We can set other variables that effect how a path is stoked too,”; “stoked” should be “stroked.”

“Some apps might just do a little processing on the incoming audio and then drop the data on teh floor” Replace “teh” with “the”

The first full paragraph of text says something to the effect that properties were not explained yet, though they were in Seciton 2.7, and in much greater detail than is presented here. “For more details on both the proper -
ties and protocols of Objective-C see the Apple docs [?].” Perhaps that should be changed to backreference to 2.7?

Would it be possible to get more information on working with images? It’d really be helpful to have more information on things like image zoom and manipulation added. Information on dynamically loading images would really be helpful too.

In general, use Layers for screenshots so that you easily can strip away background noise - makes the book look better (which always is a good thing). It also saves time, as cropping, masking is a thing of the past.

Why is the view called “AddTeamViewController” and not only “AddTeamView”? The class that manages AddTeamView should be the AddTeamViewController - maybe? Or am I missing something here?

The code as written on this page a) adds each path twice and b) leaks memory.

The CGContextAddPath(ctx, [self pathInRect:one]); are not necessary. They also leak a reference to a CGPath.

Both the teams and addButtonItem should be assign (default) vs retain properties. When you create the NSMutableArray for teams it already has a retain count of one and by the time you assign, it then has a retain count of two. Same goes for the constructor for the addButtonItem property.

Because of this I am very confused as to why you would suggest that you call autorelease on the addButtonItem where you did not on the teams object as well.

The main code sample has "FileOverviewView" and it should be “FileOverviewViewController” for loading the nib.

end of 3rd paragraph, “involves these steps, create a new..” should be a colon instead - that is, “Building any table view based UI typically involves
these steps: create a new subclass of UITableViewController, create a new
View XIB file, switch the view for a table view, set the data source and
delegate.”

The name of the “spinner” class is UIActivityIndicatorView, not UIActivityIndicator.

Line 4: the signature of the method is “expectedContentLength” without the colon, not “expectedContentLength:”.

Regarding the text editors: you don’t need a console editor or a special launcher - you can just use the “open” command to launch your favourite editor, e.g. “open httpd.conf” or “open -a Smultron httpd.conf”. You can also press Cmd+Shift+G in Finder to show a “go to folder” dialog, enter /etc/apache2, and do whatever you want with the file once the folder contents are displayed.
(One caveat: Textedit seems to be unable to save a file owned by root, but Smultron has no problems with it, it just asks to authenticate).

I think I know what you meant, but “user is often never aware” sounds a bit weird…

“Every iPhone object must have a single UIWindow object” -> did you perhaps mean “every iPhone application” ?…

Re #37622: I personally don’t find the phrase “You’ve done it” offensive in any way…

Missing a comma after “well” in " it (well technically"

See “chap.mediaplayback” in “oundation, Core Audio, and Quartz / Core
Graphics, and will be introduced in the (as yet) unwritten
chap.mediaplayback.”

“There are two new concepts here” - not true, see earlier examples.

The “teamTextField” and “view” Outlets should be
assigned.

ALSO - the Navigation..

in viewDidLoad, do you needs to call to [super viewDidLoad]? before or after the content for this class? The template has the call in it…

last sentence of paragraph 2: … we are going to start introduce you to …

3rd paragraph first sentence:
“On the left side below the toolbar is the file/resource list.” — It’s on the right side.

Some references in your latex document are not right -> [?]

On my Kindle, this graphic (Kindle location 205) and the next graphic (Kindle location 215) show up as a tiny, unreadable graphic at the lower left-hand corner of a large black rectangle.

“Also, since this is the first time we’re referring to RootViewController from
within AddTeamViewController.h we’ll need to import it.” - instead of importing, it would be better to use the @class keyword to just declare it.

“In addButtonWasPressed we’re going to load a new AddTeamViewController from its AddTeamViewController nib file.” - I think this is a bit inaccurate, because the controller object itself isn’t loaded from the nib - it’s just created, and only after that it loads the nib with the view.

“Because textFieldShouldReturn: is a method of UITextFieldDelegate’s pro-
tocol, we need to declare that our AddTeamViewController fulfills the
UITextFieldDelegate” -> this is a bit redundant, because we’re already done this on page 76: “We’ll also declare that the view controller implements the UITextFieldDelegate protocol, in order to handle events related to the dismissal of the keyboard.”

“But you can set the backBarButtonItem on the navigationItem of any view controller to change the back button title (or other properties) to be anything you’d like.” -> you could add that by setting backBarButtomItem, you change what’s displayed when the given controller is BELOW the top controller, in contrast to leftBarButtonItem and rightBarButtonItem, which change what’s displayed when the given controller IS the top controller. This wasn’t obvious for me at first…

“Next we need to do the same thing we did for the ByPoplulationViewController. First delete the existing view, then add a table view to the xib file.” -> This is NOT the same, because in ByPopulationViewController we were told to add the table view into the existing view, not replace the existing view with a table view.

Also, Population not Poplulation (in the name of the controller).

“Congratulations. You have been through all the view controllers that
come with Cocoa Touch.” - No, I haven’t! There’s still the Image Picker Controller, which will be introduced in chapter 13 :)

bottom paragraph: “However is the view is not set then the view controller checks to see if its nib file is set.” - I believe this should read “however if the view…”

I think this line in the sample code will need updating for the 3.0 revision of the book:

cell = [[[UITableViewCell alloc] initWithFrame:CGRectZero
reuseIdentifier:CellIdentifier] autorelease];

I dont know if I can give much more detail due to the nda. try it and you’ll see why it doesnt work

“we’ll set up variables for the ball’s location and position” should maybe be “we’ll set up variables for the ball’s location and velocity”.

second Paragraph from the bottom reads

“Let’s look ah how to launch Safari with this mechanism. ”

Should be

“Let’s look at how to launch Safari with this mechanism. ”

Thanks - keep up the fantastic work.

[V]iewDidLoad code sample missing Download link — this is helpful when the class name is the last word (makes it easy to know which file we’re editing).

I think the part on flippable views will eventually need rewriting for 3.0. unless I’m doing something stupid, they’ve changed the utility template again. no more RootViewController class, etc

Paragraph 4 Sentence 2:

‘Bring up its Inspector with Get Info (D I or the “Info” toolbar button) and choose the “Variables” tab.’

Should be Variables section of the “Arguments” Tab

In the setDirectoryPath: method you should perform the [p retain] before doing the [directoryPath release]. Otherwise, if both point to the same string it would be possible for the string to be deallocated and removed from memory which would cause the [p retain] to explode in your face. I know it’s an unlikely scenario but it’s still best practice.

When implementing MPMoviePlayer, should you no release the instance? With the current code, every subsequent tap of ‘play’ causes a flicker at the beginning of the clip.

“for the preferences.. ” - two dots at the end of the sentence

In the home address keys array,kABPersonAddressStreetKey is shown twice. The second one should bekABPersonAddressStateKey, based on the corresponding value.

From PDF:

CFStringRef keys[4] = {kABPersonAddressStreetKey,
kABPersonAddressCityKey,
kABPersonAddressStreetKey,
kABPersonAddressZIPKey};

CFStringRef values[4] = {CFSTR(“765 Four St.”),
CFSTR ("Fivesville"),
CFSTR ("CO"),
CFSTR ("80424")};

“notMainWindow.xib” -> missing space (at least that’s how Preview shows this)

“we’ve given the FlipSideViewController the methods uses24Hour, setUses24Hour, selectedTimeZone, and setSelectedTimeZone” - did we? I don’t remember doing that… I understand that you probably meant something like “Please add those methods now yourself, or look how it’s done in the example code that you can download” - but it’s confusing for the reader… it sounds like something that should already be there, but is not.

You could use the NSTimer’s method scheduledTimerWithTimeInterval:target:selector:userInfo:repeats: - that would be much simpler.

In the downloadable code for FlippingPreferableClock, in the last line of RootViewController#setMainViewFromPrefs, the casting to (NSString*) is not necessary, because prefTimeZone is already an NSString.

IMHO it would be more natural to store the 24-hour preference as a BOOL wrapped in an NSNumber, instead of a "YES"/“NO” string. But that’s just my opinion…

First line, ‘where an row’ should read ‘where a row’

You say that the settings icon should be named Icon.png and located inside the Settings bundle; this is incorrect. If I copy an icon inside the bundle, it doesn’t even show up in XCode. Instead, the icon should be named Icon-Settings.png and put in the project bundle root, next to the Settings bundle.
If there is no settings icon, iPhone tries to use the main application icon, with a name specified in Info.plist (which, by default, is Icon.png), but this one must be sized 57x57.

I think it’s worth mentioning that the NSUserDefaults way of storing preferences is also available when you have your own preferences screen inside the application, like in the first part of the chapter (and it’s probably easier to use than the method with saving an NSDictionary to a file manually). Right now, the reader might get an impression that you can only use NSUserDefaults if you have a Settings bundle for Preferences application.

I just spent half my day messing around with scroll views before finding a video that happened to mention the property I needed to set (contentSize) to actually get it to scroll. This property isn’t exposed in IB (at least in the version that ships with the first release of the 3.0 SDK), so you have to set it programatically. I couldn’t find any mention of UIScrollView in the book, and it would have saved me a lot of time.

Referring to the first paragraph (describing using NSSearchPathForDirectoriesInDomains() to get the path of the Documents folder). This technique is used in the previous chapter to generate the file path for the preferences file (p.141) with no information given about it at that time.

I’d suggest moving the p.160 description back to then.

Not in the book (had to put in a page#), but rather the sample code: FileIO/DatabaseShoppingList/DatabaseShoppingListAppDelegate.m

In applicationDidFinishLaunching:, when setting up the tab bar controller, and specifically the array of controllers for it, you’ve used an NSMutableArray as a workaround instead of a standard NSArray:

\t// initWithObjects should be a perfectly good way to create the array of controllers
\t// for the tab bar, and works fine in the simulator, but leads to an EXC_BAD_ACCESS
\t// on the phone in 2.0 (5a345). workaround here is to use an NSMutableArray.
\t// NSArray *controllers = [[NSArray alloc] initWithObjects: addItemViewController, listByPriceViewController];

The problem is that it’s missing the final nil - the last line should be:
\tNSArray *controllers = [[NSArray alloc] initWithObjects: addItemViewController, listByPriceViewController, nil];

Works fine then :D

The end of the last sentence of the second paragraph should read: “…to your heart’s content.”