The most dreaded errors could be caused by InterfaceBuilder

EXC_BAD_ACCESS and SIGABRT error are the most dreaded errors when coding with Xcode, mostly it is caused by improper memory management, but past couple days I noticed it could be caused by missing connections in InterfaceBuilder as well as the "missing identity" when setting up the Tab Bar
To fix the problem I reconnected the Outlets in the ViewControllers to the controls inside the Views, also set the Class on the identity's tab:
Just a self reminder another more common reason for the EXC-BAD-ACCESS error, is accessing member variable directly instead of using self.@property in the init(), which cause the member variable not retained.

Why cannot they give us more meaningful error messages?

Migrating Cocoa code to iOS

Ran into a couple things in this process.
#1. Turning AutoResizing off finally made the custom view display properly
#2. Custom View was nil at run time, double-check the Interface Builder connections

Extra effort was put into migrating from Cocoa to CoreGraphic/Quartz2D.............

Updated the Mac Prototype a little bit

Implemented the file loading over the web, identified a couple issues in need to be fixed
1) The Comments tag still need to be further parsed
2) Comments TextArea need to be clear before each move-or shown in an accumulative way more specifically older comments in faded fonts.
3) Also noticed that I may have a lot clean-up to do regarding Memory Mmanagement-retain, autorelease and all the other good stuff.

Completed Test #8-Building UITableView from Json data

A couple things left and need to do next:
1) remotely load file into a view
2)save file locally and save path into the database....