[ad_1]
UITableView
So let’s begin with a regular single-view template for iOS. Title the challenge, and go straight to the Essential.storyboard file. Choose your ViewController, delete it and create a brand new UITableViewController scene.
Set the desk view controller scene as preliminary view controller and create a TableViewController.swift file with the corresponding class.
import UIKit
class TableViewController: UITableViewController {
var dataSource: [String] = [
"Donec id elit non mi porta gravida at eget metus.",
"Integer posuere erat a ante venenatis dapibus posuere velit aliquet. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus.",
"Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Vestibulum id ligula porta felis euismod semper. Nullam id dolor id nibh ultricies vehicula ut id elit. Nullam quis risus eget urna mollis ornare vel eu leo.",
"Maecenas faucibus mollis interdum.",
"Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras mattis consectetur purus sit amet fermentum.",
"Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Maecenas faucibus mollis interdum.",
]
}
extension TableViewController {
override func tableView(_ tableView: UITableView, numberOfRowsInSection part: Int) -> Int {
return self.dataSource.rely
}
override func tableView(_ tableView: UITableView, cellForRowAt indexPath: IndexPath) -> UITableViewCell {
let cell = tableView.dequeueReusableCell(withIdentifier: "Cell", for: indexPath) as! TableViewCell
cell.dynamicLabel?.textual content = self.dataSource[indexPath.row]
cell.dynamicLabel.font = UIFont.preferredFont(forTextStyle: .physique)
return cell
}
}
The setup is de facto self-descriptive. You have bought a string array as knowledge supply, and the required implementation of the UITableViewDataSource protocol.
The one factor that’s lacking is the TableViewCell class.
class TableViewCell: UITableViewCell {
@IBOutlet weak var dynamicLabel: UILabel!
}
Firstly, create the category itself, then with interface builder choose the desk view controller scene and drag a label to the prototype cell. Set the category of the prototype cell to TableViewCell. The reusable identifier may be merely “Cell”. Join the dynamicLabel outlet to the view. Give the label high, backside, main, trailing constraints to the superview with the default worth of 8. Choose the label, set the font to physique model and the traces property to zero. That is how easy it’s. 😂
Now you’re nearly prepared. You simply have to set the estimated row top on the desk view. Contained in the TableViewController class change the viewDidLoad methodology like this:
override func viewDidLoad() {
tremendous.viewDidLoad()
self.tableView.estimatedRowHeight = 44
self.tableView.rowHeight = UITableView.automaticDimension
}
The estimatedRowHeight property will inform the system that the tableview ought to attempt to determine the top of every cell dynamically. You must also change the rowHeight property to automated dimension, should you do not do then the system will use a static cell top – that one from interface builder that you would be able to set on the cell. Now construct & run. You could have a beautiful desk view with self sizing cells. You possibly can even rotate your system, it’ll work in each orientations.
Another factor
In case you change the textual content dimension below the iOS accessibility settings, the desk view will mirror the adjustments, so it’s going to adapt the structure to the brand new worth. The font dimension of the desk view goes to vary accordint to the slider worth. You would possibly need to subscribe to the UIContentSizeCategory.didChangeNotification in an effort to detect dimension adjustments and reload the UI. This function is known as dynamic kind.
NotificationCenter.default.addObserver(self.tableView, selector: #selector(UITableView.reloadData), identify: UIContentSizeCategory.didChangeNotification,, object: nil)
UICollectionView
So we have completed the straightforward half. Now let’s attempt to obtain the identical performance with a group view. UICollectionView is a generic class, that’s designed to create customized layouts, due to this generic behaviour you will be unable to create self sizing cells from interface builder. You need to do it from code.
Earlier than we begin, we are able to nonetheless play with IB slightly bit. Create a brand new assortment view controller scene, and drag a push segue from the earlier desk view cell to this new controller. Lastly embed the entire thing in a navigation controller.
The cell goes to be the very same as we used for the desk view, but it surely’s a subclass of UICollectionViewCell, and we’re going to assemble the structure instantly from code.
class CollectionViewCell: UICollectionViewCell {
weak var dynamicLabel: UILabel!
required init?(coder aDecoder: NSCoder) {
fatalError("init(coder:) has not been applied")
}
override init(body: CGRect) {
tremendous.init(body: body)
self.translatesAutoresizingMaskIntoConstraints = false
let label = UILabel(body: self.bounds)
label.translatesAutoresizingMaskIntoConstraints = false
label.font = UIFont.preferredFont(forTextStyle: .physique)
label.backgroundColor = UIColor.darkGray
label.numberOfLines = 0
label.preferredMaxLayoutWidth = body.dimension.width
self.contentView.addSubview(label)
self.dynamicLabel = label
NSLayoutConstraint.activate([
self.contentView.topAnchor.constraint(equalTo: self.dynamicLabel.topAnchor),
self.contentView.bottomAnchor.constraint(equalTo: self.dynamicLabel.bottomAnchor),
self.contentView.leadingAnchor.constraint(equalTo: self.dynamicLabel.leadingAnchor),
self.contentView.trailingAnchor.constraint(equalTo: self.dynamicLabel.trailingAnchor),
])
}
override func prepareForReuse() {
tremendous.prepareForReuse()
self.dynamicLabel.font = UIFont.preferredFont(forTextStyle: .physique)
}
func setPreferred(width: CGFloat) {
self.dynamicLabel.preferredMaxLayoutWidth = width
}
}
We’ve a subclass for our cell, now let’s create the view controller class. Contained in the viewDidLoad methodology it’s important to set the estimatedItemSize property on the gathering view. There should you give fallacious dimension, the autorotation will not work as anticipated.
override func viewDidLoad() {
tremendous.viewDidLoad()
self.navigationItem.rightBarButtonItem = UIBarButtonItem(barButtonSystemItem: .refresh, goal: self, motion: #selector(self.toggleColumns))
self.collectionView?.register(CollectionViewCell.self, forCellWithReuseIdentifier: "Cell")
if let flowLayout = self.collectionView?.collectionViewLayout as? UICollectionViewFlowLayout {
flowLayout.itemSize = CGSize(width: 64, top: 64)
flowLayout.minimumInteritemSpacing = 10
flowLayout.minimumLineSpacing = 20
flowLayout.sectionInset = UIEdgeInsets(high: 10, left: 10, backside: 10, proper: 10)
flowLayout.estimatedItemSize = CGSize(width: self.preferredWith(forSize: self.view.bounds.dimension), top: 64)
}
self.collectionView?.reloadData()
NotificationCenter.default.addObserver(self.collectionView!, selector: #selector(UICollectionView.reloadData), identify: UIContentSizeCategory.didChangeNotification, object: nil)
}
Contained in the rotation strategies, it’s important to invalidate the gathering view structure, and recalculate the seen cell sizes when the transition occurs.
override func traitCollectionDidChange(_ previousTraitCollection: UITraitCollection?) {
tremendous.traitCollectionDidChange(previousTraitCollection)
guard
let previousTraitCollection = previousTraitCollection,
self.traitCollection.verticalSizeClass != previousTraitCollection.verticalSizeClass ||
self.traitCollection.horizontalSizeClass != previousTraitCollection.horizontalSizeClass
else {
return
}
self.collectionView?.collectionViewLayout.invalidateLayout()
self.collectionView?.reloadData()
}
override func viewWillTransition(to dimension: CGSize, with coordinator: UIViewControllerTransitionCoordinator) {
tremendous.viewWillTransition(to: dimension, with: coordinator)
self.collectionView?.collectionViewLayout.invalidateLayout()
self.estimateVisibleCellSizes(to: dimension)
coordinator.animate(alongsideTransition: { context in
}, completion: { context in
self.collectionView?.collectionViewLayout.invalidateLayout()
})
}
There are two helper strategies to calculate the popular width for the estimated merchandise dimension and to recalculate the seen cell sizes.
func preferredWith(forSize dimension: CGSize) -> CGFloat {
var columnFactor: CGFloat = 1.0
if self.twoColumns {
columnFactor = 2.0
}
return (dimension.width - 30) / columnFactor
}
func estimateVisibleCellSizes(to dimension: CGSize) {
guard let collectionView = self.collectionView else {
return
}
if let flowLayout = self.collectionView?.collectionViewLayout as? UICollectionViewFlowLayout {
flowLayout.estimatedItemSize = CGSize(width: self.preferredWith(forSize: dimension), top: 64)
}
collectionView.visibleCells.forEach({ cell in
if let cell = cell as? CollectionViewCell {
cell.setPreferred(width: self.preferredWith(forSize: dimension))
}
})
}
You possibly can even have a number of columns should you do the suitable calculations.
There is just one factor that I couldn’t clear up, however that is only a log message. In case you rotate again the system a number of the cells will not be going to be seen and the structure engine will complain about that these cells can’t be snapshotted.
Snapshotting a view that has not been rendered ends in an empty snapshot. Guarantee your view has been rendered at the least as soon as earlier than snapshotting or snapshot after display updates.
If you may make this message disappear in some way OS_ACTIVITY_MODE=disable, please do not hesitate to submit a pull request for the tutorials repo on github. 😉
[ad_2]
