Sunday, March 15, 2009

SXSW - iPhone Dev

Dave strongly suggested I go to this...so here's some notes.


browser devs don't consider system resources when developing
browsers have built in status/progress indicators
iphones don't have any of that – how to do that?

Iphones are asynchronous and should think consider multithreading
Objective-C, what is it?
C w/OO added
Different from web languages
pointers
memory management
non-linear code execution
syntactical old-school
Gotta use Xcode
Cocoa – the display/interface framework – interactions are asynchronous

Protocols
https, u/p authenticated, REST, JSON (rest is considered best practices because it's lighter)

Demo & Tutorial:
MVC, events & delegates
Use Xcode to pull templates down onto the gui
AppDelegate is like the master controller and is where the app is initialized – has to be AppDelegate.m
below that sits models and views


Memory Management
if you alloc/init then you have to release it
if you don't, do not release cause you could cause exception
use instruments to profile apps, cause you need to be able to respond to release memory request

No comments:

Check out Israel and Egypt photos here
Check out my Egypt photos here