In This Chapter
Adding a button in Interface Builder
Using the Target-Action design pattern to implement a button touch in your code
Finding out what Web views do
Using the phone-number-detect feature of Web views to initiate a call
Admiring the final ReturnMeTo listing
Developers tend to be optimistic when they put what they hope will be the finishing touches to their latest application. You've expended a certain amount of time and effort making your dream app a reality — okay, maybe not blood, sweat, and tears, but a lot of work nevertheless — and you tend to think that your efforts will be greeted with great praise.
The reality, more often than not, is that when you take your spanking new application around to a few friends and colleagues it isn't always instantly welcomed as the newest, most advanced thing since sliced bread! Sure, it gets some praise, but there are some criticisms as well — "helpful suggestions" is how your friends put it.
To take a concrete example, when I started showing around the ReturnMeTo application the way it worked at the end of Chapter 9, I got the good-news-bad-news routine.
The good news was that everyone liked it. The bad news was, they almost all made the same two comments:
Disabling editing was a good idea, but they also all thought that having to touch the label to enable it was pretty hokey. "Make the iPhone image a button" was suggested by more than one person.
The second comment was, "Why can't I just touch ...