Today, when reviewing the code, I found that the previous paging loading logic of tableview and collectview still has room for optimization, so I optimized it.
1. Comparison of the code of paging loading of tableview
The code before optimization is as follows:
[.mj_footer endRefreshing]；
[ addObjectsFromArray:feedList];
[ reloadData];
The optimized code is as follows:
NSMutableArray *indexPaths = [NSMutableArray array];
[feedList enumerateObjectsUsingBlock:^(id obj, NSUInteger idx, BOOL *stop) {
NSIndexPath *indexPath = [NSIndexPath indexPathForRow:( + idx) inSection:0];
[indexPaths addObject:indexPath];
}];
[.mj_footer endRefreshing];
[ addObjectsFromArray:feedList];
[ beginUpdates];
[ insertRowsAtIndexPaths:indexPaths withRowAnimation:UITableViewRowAnimationNone];
[ endUpdates];
2. Comparison of code for paging loading of collectonview
The code before optimization is as follows:
[ addObjectsFromArray:feedList];
if ( < kPageSize) {
[.mj_footer endRefreshingWithNoMoreData];
}else{
[.mj_footer resetNoMoreData];
}
[ reloadData];
The optimized code is as follows:
NSMutableArray *indexPaths = [NSMutableArray array];
[feedList enumerateObjectsUsingBlock:^(id _Nonnull obj, NSUInteger idx, BOOL * _Nonnull stop) {
[indexPaths addObject:[NSIndexPath indexPathForItem:( + idx) inSection:0]];
}];
[ addObjectsFromArray:feedList];
if ( < kPageSize) {
[.mj_footer endRefreshingWithNoMoreData];
}else{
[.mj_footer resetNoMoreData];
}
[ insertItemsAtIndexPaths:indexPaths];
Summary: In comparison, the code volume seems to have increased a little after optimization, but theoretically the performance of paging loading is better. The global refresh used in the previous pagination loading, and the local refresh was used after optimization. This improves performance.
The above is all the content of this article. I hope it will be helpful to everyone's study and I hope everyone will support me more.