One of the memories of WWDC last year for myself was sitting in the auditorium and listening about allowing iOS to calculate the height for
each of the UITableViewCell's inside a UITableView and thus allow for the developer to no longer implement the delegate to calculate the height
for the row at each indexPath. This functionality is definitely useful if apple implemented it correctly and
there were no underlying bugs in it. With iOS8.3 the solution finally seems to be stable and not have any issues with the UIScrollView
content offsets when coming back to the UIViewController holding the UITableView from another
UIViewController.
Objective-C as a language has been around since the early 1980s and thus is a very mature language compared to the newer languages such as Swift which Apple introduced at WWDC 2014. While Swift is a breath of fresh air in sense of having the Apple development community very excited we cannot ignore the fact that many of Apple's current frameworks are for the majority written in Objective-C. With this in mind this post attempts to discuss runtime object association which is one of the useful features found in the Objective-C runtime.
I have seen this a lot where users on sites such as Stack Overflow
have issues with the iOS UIView hierarchy. Many of the questions are related too how do i make a view stay behind
another view or how do i make a view be the bottom view of the UIViewController.
When working with a UIViewController one of the most used pieces of functionality is dismissing the view
controller. As more and more projects where created and more and more UIViewController classes were created
it was noticed that the same piece of code was continually being written over and over again.