iPhone programming

malef!c

malef!c

malef!c

Associate
Joined
27 Jun 2006
Posts
1,473
Hi guys.

Anyone coding anything for the iPhone / Touch?

Could you recommend any books for a beginner to the Apple SDK side of life as well as a decent beginners book to the C bit of it all.

I have coded in C and a small amount of C++ many years so hopefully this will help a bit!

Cheers
M.
 
I can't recommend you book as I've never read a book on the Apple SDK. All I used was the

http://developer.apple.com/mac/

There are hefty Objective-C language tuts in there if you dig deep, learn Objective-C and then learn the basic cocoa framework which shared between the Iphone and mac.

The UI stuff is different between mac and iphone though, just dig through the iphone develepment website.

If you want to sort out your C programming first i'd recommend K&R C Programming.
 
Thanks for that - have a couple of C books on order to brush that up and then will have a crack at the Apple side of life.

Will have a look throught the developer section of Apple for the example code.

M.
 
I'm currently coding a few apps for the iPhone. I wouldn't bother trying to learn C - it's an archaic language and although the syntax is similair-ish to Objective C, C is a procedural language and like C++, Objective C is object-orientated.

I personally don't like Objective C too much, but it's kind of necessary if you want to use Cocoa and such. You can also develop in C++ and combine both C++ and Objective C in one source file. There are some tricks to this though and it isn't quite that straight forward but it's doable. If you want help with this, let me know.

As far as books go, have a look at the Apple developer website. I've got some books at work for iPhone dev, but some of them are a bit rubbish and I can't remember what the good one is titled.
 
Thanks for the offer of some help - I think I will be starting this next week so no doubt will be back asking some questions!!
 
Mystique said:
I'm currently coding a few apps for the iPhone. I wouldn't bother trying to learn C - it's an archaic language and although the syntax is similair-ish to Objective C, C is a procedural language and like C++, Objective C is object-orientated.

I personally don't like Objective C too much, but it's kind of necessary if you want to use Cocoa and such. You can also develop in C++ and combine both C++ and Objective C in one source file. There are some tricks to this though and it isn't quite that straight forward but it's doable. If you want help with this, let me know.

As far as books go, have a look at the Apple developer website. I've got some books at work for iPhone dev, but some of them are a bit rubbish and I can't remember what the good one is titled.
Click to expand...
Objective C is the C Syntax with smalltalk syntax. All c code is valid objective C code.

Smalltalk is a proper oo language, and that's why a lot java and C++ people don't really understand it because they are not true oo languages even the creaters admit it(stroustroup).

For example I've seen people make factory objects, when you can get the class object (different from object instance) to do the same thing.
 
Last edited:
Brilliant - thats the one I ordered!

Hopefully I will be able to borrow a Mac Mini from work to start playing with the SDK next week so I will be back no doubt :)
 
UK|AL said:
Objective C is the C Syntax with smalltalk syntax. All c code is valid objective C code.

Smalltalk is a proper oo language, and that's why a lot java and C++ people don't really understand it because they are not true oo languages even the creaters admit it(stroustroup).

For example I've seen people make factory objects, when you can get the class object (different from object instance) to do the same thing.
Click to expand...

I'm not disputing any of that, I'm just saying that C is a legacy language and in terms of design/paradigm, is pretty damn different to an OO language. Sure learning C might help with a few bits of syntax here and there, but that's about it.

Also the example you state is surely a design choice rather than a langauge deficiency (if I understand your ambiguous naming of 'class object' correctly).

EDIT: Looking at the book numnutz posted, that's the book I was trying to remember in my previous post.
 
You must log in or register to reply here.
Back
Top Bottom