On Apr 6, 2010, at 3:29 PM, Jens Alfke wrote:
> I have to confess that I haven't yet learned UIKit. The bits of iPhone
> development I've done so far have used networking and crypto APIs, and
> CoreAnimation, but hardly any of the UIKit classes.
>
> What would be the best book for me to learn from? Obviously most of the books
> out there don't assume you know Objective-C or Foundation or even Xcode, and
> will take time teaching those. I'd rather not have to buy or skim through
> stuff like that. Are there any books that assume you already know Cocoa
> programming and just cover what's different on the iPhone OS?
As Bob Estes said, the Dave Mark / Jeff LeMarche books are pretty good.
Apart from that,
o the programming concepts of the iPhone focus on presenting single screens
of content
o each screen of content is represented by a single UIView that is the root
of a view hierarchy
o each of those single views is in turn managed by a UIViewController or one
of its sub-classes
o there are various schemes for navigating between screens
So the architecture of a good iPhone application is determined by the screens
of content and the
transitions between them. The logic of those transitions will end up being
implemented via a network
of View Controllers.
Two of the primary navigation schemes are implemented by UITabBarController and
UINavigationController
(usually in conjunction with a UITableViewController).
You see UITabBarController in action in the iPhone World Clock application.
You see UINavigationController (with UITableViewController) in the iPhone
Settings application (and
many others).
The iPhone Weather application shows another navigational scheme known as Page
Control, which
uses a UIScrollView as a 'paging' mechanism, and there's a UIPageControl widget
on the bottom to
navigate that way if you wish to.
There's no NSBezierPath parallel on the phone, so you get down into Core
Graphics a lot more than
with Appkit.
Core Data is available. The phone does not have bindings, but does have KVC
and KVO.
There's a lot more, of course, but you'll find many more similarities than
differences (apart from
UIWindow being a sub-class of UIView . . .).
I think the UIKit team did a great job in 'lowering the barriers to entry' (to
speak like a marketroid).
Cheers,
. . . . . . . . Henry_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
