UITableViewDynamicLayoutCacheHeight Download - UITableViewDynamicLayoutCacheHeight Source code download

UITableViewDynamicLayoutCacheHeight

AI Source Code

5.1.8

Download

introduce

UITableViewDynamicLayoutCacheHeight is a convenient, high-performance automatic calculation of the height of UITableViewCell and UITableViewHeaderFooterView using Autolayout layout [ Xib , StoryBoard , Masonry , SnapKit , SDAutoLayout ...], supports horizontal and vertical screens, automatically manages the height cache internally, and is compatible with Swift.

Installation with CocoaPods

 pod 'UITableViewDynamicLayoutCacheHeight'
pod install
#import <UITableViewDynamicLayoutCacheHeight/UITableViewDynamicLayoutCacheHeight.h>

If you only want to use registration-free access to Cell and UITableViewHeaderFooterView, you can use the following pod

 pod 'UITableViewDynamicLayoutCacheHeight/Category'

Installation with Carthage

Carthage is a decentralized dependency manager that builds your dependencies and provides you with binary frameworks. To integrate UITableViewDynamicLayoutCacheHeight, add the following to your Cartfile.

 github "liangdahong/UITableViewDynamicLayoutCacheHeight" ~> 5.2 . 0

Manual installation

Download the project [ clone https://github.com/liangdahong/UITableViewDynamicLayoutCacheHeight.git ]
Drag and drop the entire contents of the UITableViewDynamicLayoutCacheHeight folder into your project.

Graphic instructions for use

`Cell` is built using `Xib` "It also supports pure code layout, as long as Autolayout is used."

Create your Cell and use constraint layout, make sure [the views in the cell are laid out from top to bottom, and the MaxY of the bottom view is exactly the required height of the cell] [do not set bottom constraints, just lay out from top to bottom] , internally it will automatically obtain the bottom View and then use its MaxY as the height required by the Cell. You can view the acquisition process in lines 144~167 of the code, and then perform various caching operations]

Implement the following code in the proxy method of getting the height of UITableView. The code in Block is consistent with the code in - (UITableViewCell *)tableView:(UITableView *)tableView cellForRowAtIndexPath:(NSIndexPath *)indexPath .

Now your UITableView has自动算高and自动缓存高度. The effect is as follows:

Swift Xib Demo
Swift pure code layout demo
For more usage, please refer to the API of the UITableView+BMDynamicLayout.h file.

Framework implementation principle

Height calculation principle

Create the Cell in advance, then fill in the content, then force layout, then get the View with the largest MaxY in the Cell, and then take the MaxY of this View to be the height required by the Cell [so保证Cell 中的View 的MaxY 最大的值即为Cell 需要的高度Crucial], the cache saving and clearing operations are automatically managed internally.

question

Everyone should be well aware of the shortcomings of the system's automatic high calculation, such as: no caching, repeated calculations, interface jumps, and because it is scrolling and calculating in cells with complex layouts, there are some problems. It only supports iOS8+, and the layout must fill the entire Cell. In the layout In some scenarios, priority needs to be set, otherwise constraint conflicts will be reported.
UITableView-FDTemplateLayoutCell I used this framework at the beginning. At the same time, the API design was also based on FDTemplateLayoutCell. I also used a few materials. Thanks for this, but there are some bugs that have not been solved. The layout must fill the entire Cell. Some scenes need to set priorities during layout, otherwise constraint conflicts will be reported, so they were migrated to UITableViewDynamicLayoutCacheHeight.
The defects of UITableViewDynamicLayoutCacheHeight are:
- ① One more View may be added [You can add the bottom distance to the calculated result, but this is not recommended]
- ② The code to configure Cell must be written in two places, similar to UITableView-FDTemplateLayoutCell.
Based on this framework, a simple WeChat Moments function was implemented. The WeChat Moments code was casually written a few years ago? I am not ready to adjust it. If you are interested, you can take a look.

Frequently Asked Questions

If you use key for caching, it means that the height is only related to the key. As long as you use the same key, you will get the same height. This height will never be refreshed internally (even if reloadData is called).