Accessorizer I have been told if you do any kind of serious development in Objective C this is the tool to use. At 15 bucks I'll be making it part of my Objective C toolbox especially since I hate typing out all those accessors (variables, @property @synthesize.) The time saved will surely out weigh the cost.

When starting a new project you have the ability to  select a template of premade projects. Two examples of this are
    1. Navigation Based Application
    2. View Based application

When these templates are selected xCode will create the appropriate base controller for you in interface builder, such as "Navigation Controller" or a "View Controller" it will also create the appropriate classes for you with some of the most commonly used delegate and datasource methods along with the appropriate methods to override.

With a new project and selecting Window-based application, you are simply creating a blank slate in which you have to create nearly everything. It's rarely advantageous to use this unless, you are creating something outside the templates offered or you are learning how all the pieces fit together.

I saw this picture on Dave Mark's blog. Dave is a very talented Objective C developer. The picture really got me so I had to post it.

Enjoy.

What a wild month! London, Paris (loved Paris), and Barcelona, followed up with a gig in Philly working for the second biggest software developer in the world on their up front website, SAP.com. Before I dive into the limited aspects I can speak about SAP.com's technology I would like to point out the facet of SAP that has had, and will have, a lasting effect on me, the cafateria. These people (SAP) treat their people good! Made to order sushi, made to order Thai, a Philly cheese steak that will challenge South Philly's finest and a Starbucks that feels like it was made just for me, all this within a short walk from my desk. Really, next to the BMW the Germans know how to do it.

Lets dive into my first day. I was sitting at my desk, after enjoying my oh-so-delicious lunch of Alaskan Cod; I hear this loud noise getting louder. Turns out it was a helicopter flying in with the American Co-CEO. As he gets out, much like a scene you might expect to see from Iron Man, he has a dream effect on me. He waves at the people there to greet him and follow's up with a mock gun shot (I can only hope he made the clicking sound that goes with the mock gun shot) at one of the security guards as he steps into the Escalade, in my mind I say YES, awesome! I know right then and there I'm going to love it for my limited time here.

I digress lets talk about a website that needs to address more nations than a senator trying to get votes in NYC. In short, because this is all I will say and feel comfortable, they follow a Model View Presenter (MVP) development process in making their site. SAP's site addresses content based on what nation/region you are coming from all while maintaining a similar look and feel for every end user. Think localization is easy with .Net...not on this scale boys and girls! Now add a level complexity comprising of several teams in more countries than you can count on one hand, developing for this one site. To create a level of consistency across so many sites a template format was built and an engine on top of the .Net engine to address what should be displayed....this is all I will give up, but I can say it's fun and challenging.

Thanks to VML for making this small yet, incredible contract, possible.

The Problem:
I was getting a white screen with no data in a UITableView on it in the iPhone simulator.

The Solution:
I had my initialization code for the array in the the "loadView" method and not the "viewDidLoad" method

Explanation:
Don't read self.view in -loadView. Only set it, don't get it. The self.view property accessor calls -loadView if the view isn't currently loaded. There's your infinite recursion. I'm guessing UITableView calls a View [pretty good guess since "view" is in the name. :)] which in turn caused my recursion.

This was a stupid little error that caused me about 30 minutes of my life due to the fact I didn't get any build errors. A simple copy and paste moved me forward.

Update: I think it might be important to distinguish the differece between loadView and viewDidLoad. (below)

loadView is the method in UIViewController that will actually load up the view and assign it to the "view" property. This is also the location that a subclass of UIViewController would override if you wanted to programatically set up the "view" property. viewDidLoad is the method that is called once the view has been loaded. This is called after loadView is called. It is a place where you can override and insert code that does further initial setup of the view once it has been loaded.