Original post https://github.com/onmyway133/blog/issues/154
The most common UI element in iOS is
UITableView, and the most common task is to display the UITableViewCell using the model.
Although the title specifies UITableViewCell, but the problem involves other views (UICollectionView, custom view, ...) as well
There are many debates about this, so here I want to make a summary, all in my opinion
UITableViewCell Is Not a Controller
This article follows strict MVC and states we should not pass model object to cell and let cell manipulate directly on the model. He shows several examples that point out this job is not suitable for the cell. Instead this job should be done on the Controller (UIViewController, UITableViewDataSource, ...)
Skinnier Controllers Using View Categories
This article states that we should keep ViewController skinnier by transfering the job (mapping model object to cell) to the cell category
UITableViewCell Is Not a Controller, But…
This articles explains the beauty of subclassing to take advantage of Polymorphism. In the theming example he gives, we see that Controller 's job now is to select the correct cell subclass, and the subclass 's job is to know how to use the model
"When a UITableViewCell subclass accepts a model object parameter and updates its constituent subviews as I have described, it is behaving as a data transformer, not a controller"
Model View Controller Presenter
This article shows that using subclassing and category will have duplication implementation when you have more cells and models. After several optimizations, he finally gets to the Model Presenter, which is the center object who knows how to represent the model in different view.
"This is an object that knows how to represent every aspect of a certain model"
MVC, MVVM, FRP, And Building Bridges
This article explains MVVM but it touches our problem directly. The problem with cell and model actually is
- How to map the model to the cell
- Who will do this job? The cell, Controller or another Model Mapping object ?
The ViewModel is actually who does this work, which is to transform the model to something the view can easily use
"A table view data source is none of these things. It’s purely a layer between the table view and the model. The model defines lists of things, but the table view data source transform those lists into sections and rows. It also returns the actual table view cells, but that’s not what I’m focusing on here. The key is its role as a middle-tier data transformer."
Paul on UITableViewCell
Brent follows with another post explaining how cell 's subviews should not be accessed outside of the cell
Clean table view code
This article deals with Bridging the Gap Between Model Objects and Cells.
"At some point we have to hand over the data we want to display into the view layer. Since we still want to maintain a clear separation between the model and the view, we often offload this task to the table view’s data source. This kind of code clutters the data source with specific knowledge about the design of the cell. We are better off factoring this out into a category of the cell class"
This together with Lighter View Controllers shows a practical example that deals with most cases