The UITableView is a class we all have used at least once in our apps.
Sometimes we need a UITableView with cells all equal in height, but sometimes we need dynamic height cells, each one having a different height, typically dependent on its own content.
The old way
Before iOS8, this was not trivial since the system needed to know in advance the overall height of the table in order to set the content size of the scrolling area (UITableView inherits from UIScrollView).
iOS8 SDK introduces a new concept: the “layout margins”. A new property has been added to the UIView class:
|
1 |
var layoutMargins: UIEdgeInsets |
These 4 values (the UIEdgeInsets fields) represent the margins of the view. Its subviews can now be positioned relative to these margins.
For example, this is the result of an inside view whose leading space to the superview is 0 (relative to margin):
In the spirit of the new iOS adaptive philosophy, the SDK itself is giving us a new (or an old modified) View Controller that is really adaptive: the UISplitViewController.
“UISplitViewController is really a workhorse to be used in iOS 8” (from WWDC 2014 session “What’s New in Cocoa Touch”).
Indubbiamente, rispetto ad altri grandi cambiamenti come un linguaggio di programmazione completamente nuovo, alcune novità del nuovo SDK introdotte nell’ultima WWDC (2014) hanno avuto minore risonanza.
Una di queste è sicuramente l’entrata in scena nella piattaforma iOS delle Size Classes: di cosa si tratta?
