iPhone development emergency guide
mattgemmell.com
iPhone development emergency guide
1–10 of 24 posts
Re: iPhone development emergency guide
#2- You have to use a Mac to develop iPhone apps.
- You have to use Xcode as your IDE.
- You have to use the Objective-C language
- You have to manage your memory manually.
- You have to have a certificate in order to sign your code to make it work on a device.
- You have to pay a yearly fee ($99) to get the ability to create such a certificate.
- You’ll have to provide various pieces of information, and enter into a distribution contract with Apple.
- Apple has to approve your app before it goes onto the App Store.
Seems a little restrictive. Imagine the antitrust concerns this would bring up if the platform actually did become dominant.
Re: iPhone development emergency guide
#3I'd like to see more of this type of thing. When learning a new language, I don't need an introduction to the if statement or while loops, yet in the interests of completeness many programming books include a thorough (and mind-numbing) guide to them. For some readers that's called for, but many of us are stuck reading about concepts we're already comfortable with. I'm concerned that if I don't read everything, I'll miss out of some bizarre quirk of the language, so I'm reluctant to skim, but this gets in the way of what I'm really trying to achieve - using the language to make cool stuff.
Writers of programming language books take note: I'm generally not interested in the tool. Tools are boring. No really, they are. Making cool stuff and solving hard problems is interesting and fun. Get the tool out of the way so I can get things done.
Re: iPhone development emergency guide
#4- You have to use a Mac to develop iPhone apps. - You have to use Xcode as your IDE. - You have to use the Objective-C language - You have to manage your memory manually. - You have to have a certificate in order to sign your code to make it work on a device. - You have to pay a yearly fee ($99) to get the ability to create such a certificate. - You’ll have to provide various pieces of information, and enter into a d…
It's no more restrictive than any major game console.
Re: iPhone development emergency guide
#5I'd like to see more of this type of thing. When learning a new language, I don't need an introduction to the if statement or while loops, yet in the interests of completeness many programming books include a thorough (and mind-numbing) guide to them. For some readers that's called for, but many of us are stuck reading about concepts we're already comfortable with. I'm concerned that if I don't read everything, I'll…
Agreed. I wrote a couple-page cheat sheet on Objective C, and since I've made a twice-yearly ritual out of forgetting Objective C, it's come in handy. Repeatedly.
Re: iPhone development emergency guide
#6I'd like to see more of this type of thing. When learning a new language, I don't need an introduction to the if statement or while loops, yet in the interests of completeness many programming books include a thorough (and mind-numbing) guide to them. For some readers that's called for, but many of us are stuck reading about concepts we're already comfortable with. I'm concerned that if I don't read everything, I'll…
Agreed. I wrote a couple-page cheat sheet on Objective C, and since I've made a twice-yearly ritual out of forgetting Objective C, it's come in handy. Repeatedly.
If you ever have time or inclination to share it, I could use a good cheat sheet. The closest I have now is "Objective C for C++ programmers", but it's not short enough to be a useful cheat sheet.
Re: iPhone development emergency guide
#7- You have to use a Mac to develop iPhone apps. - You have to use Xcode as your IDE. - You have to use the Objective-C language - You have to manage your memory manually. - You have to have a certificate in order to sign your code to make it work on a device. - You have to pay a yearly fee ($99) to get the ability to create such a certificate. - You’ll have to provide various pieces of information, and enter into a d…
I use Emacs and Make as my IDE (yes, it does call xcode to do the actual compile). There is at least one Ruby and one Javascript compiler you can use.
Re: iPhone development emergency guide
#8Earlier quoted context omitted.
Agreed. I wrote a couple-page cheat sheet on Objective C, and since I've made a twice-yearly ritual out of forgetting Objective C, it's come in handy. Repeatedly.
If you ever have time or inclination to share it, I could use a good cheat sheet. The closest I have now is "Objective C for C++ programmers", but it's not short enough to be a useful cheat sheet.
This was meant as an intro, but maybe it works as a quick reference too: http://cocoadevcentral.com/d/learn_objectivec/
Re: iPhone development emergency guide
#9"The equivalent to Java’s this is pretty much self."
Well no, the difference (inside a class) of:
this.foo = myshinyobject
and
foo = myshinyobject
is nothing in Java. In Objective-C,
self.foo = myshinyobject
and
foo = myshinyobject
are different. Particularly with regards to the @property (retain) magic; if you forget self.foo and use foo, then myshinyobject might get garbage collected. Which is not what you'd expect with a retained property.
Re: iPhone development emergency guide
#10- You have to use a Mac to develop iPhone apps. - You have to use Xcode as your IDE. - You have to use the Objective-C language - You have to manage your memory manually. - You have to have a certificate in order to sign your code to make it work on a device. - You have to pay a yearly fee ($99) to get the ability to create such a certificate. - You’ll have to provide various pieces of information, and enter into a d…
Not all of those are strictly true, either.