-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathJWInfiniteCycleView.podspec
45 lines (36 loc) · 2.69 KB
/
JWInfiniteCycleView.podspec
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
#
# Be sure to run `pod lib lint JWInfiniteCollectionView.podspec' to ensure this is a
# valid spec before submitting.
#
# Any lines starting with a # are optional, but their use is encouraged
# To learn more about a Podspec see http://guides.cocoapods.org/syntax/podspec.html
#
Pod::Spec.new do |s|
s.name = 'JWInfiniteCycleView'
s.version = '0.1.2'
s.summary = 'JWInfiniteCycleView provides a convenient way to have a infinitely-scrolling collection view.'
# This description is used to generate tags and improve search results.
# * Think: What does it do? Why did you write it? What is the focus?
# * Try to keep it short, snappy and to the point.
# * Write the description between the DESC delimiters below.
# * Finally, don't worry about the indent, CocoaPods strips it!
s.description = <<-DESC
Sometimes, your app’s UX designer wants infinite scroll for one of your collection views when the data displayed is limited. When a user scrolls to the very end of the data set, the first piece of data reappears on screen; if the use scrolls the other way, the last piece of data reappears.Traditionally, the solution for an infinite UICollectionView is to have a large duplicated data set (for example, 1000 * original data set) to trick the user into believing the collection view is infinite.
But, a large duplicated data will inevitably introduce extra overhead by having a large amount of UICollectionViewLayoutAttributes. Besides, what if the user is bored to death and just sits there for a day to scroll your collection view? The chance for this to happen might be small, but, after all, having a large duplicated data set is not a very elegant solution.
JWInfiniteCollectionView pads only a few extra duplicated items both at the start and end of your data set. In this way, it avoids the some overhead introduced by having a large duplicated data set.
DESC
s.homepage = 'https://github.com/Alex1989Wang/JWInfiniteCycleView'
# s.screenshots = 'www.example.com/screenshots_1', 'www.example.com/screenshots_2'
s.license = { :type => 'MIT', :file => 'LICENSE' }
s.author = { 'Alex1989Wang' => '[email protected]' }
s.source = { :git => 'https://github.com/Alex1989Wang/JWInfiniteCycleView.git', :tag => s.version.to_s }
s.social_media_url = 'http://www.awsomejiang.com/'
s.ios.deployment_target = '8.0'
s.source_files = 'JWInfiniteCycleView/Classes/**/*'
# s.resource_bundles = {
# 'JWInfiniteCycleView' => ['JWInfiniteCycleView/Assets/*.png']
# }
# s.public_header_files = 'Pod/Classes/**/*.h'
# s.frameworks = 'UIKit', 'MapKit'
# s.dependency 'AFNetworking', '~> 2.3'
end