It is not suitable to use UITableView for the entire page. There are sliding interactions up and down, and there are subscription events. So if there is too much logic in one cell, your ViewController will become bloated and difficult to maintain. My idea is to create a parent container ViewController for the entire page, add a childViewController
upper part
for a ViewController
lower part
add a UI for a ViewController
TableView, according to the background If the given interface has multiple network requests, it can encapsulate a ViewControllerModel.
The entire interface is a large scrollView, surrounded by a small scrollView. The three tableViews in the small scrollView slide horizontally (the content height of the large scrollView is the header view + the screen height, and the height of the small scrollView and tableView is the screen height). Remember to judge the tableView well. Pull-up and pull-down with large scrollView
It is not suitable to use UITableView for the entire page. There are sliding interactions up and down, and there are subscription events. So if there is too much logic in one cell, your ViewController will become bloated and difficult to maintain.
My idea is to create a parent container ViewController for the entire page, add a childViewController
upper part
for a ViewController
lower part
add a UI for a ViewController
TableView, according to the background If the given interface has multiple network requests, it can encapsulate a ViewControllerModel.
The entire interface is a large scrollView, surrounded by a small scrollView. The three tableViews in the small scrollView slide horizontally (the content height of the large scrollView is the header view + the screen height, and the height of the small scrollView and tableView is the screen height). Remember to judge the tableView well. Pull-up and pull-down with large scrollView