| { |
| "name": "CollectionKit", |
| "version": "1.3.0", |
| "summary": "A modern swift framework for building data-driven reusable collection view components.", |
| "description": "### Features\n\n* Declaritive API for building collection view components\n* Automatically update UI when data changes\n* Composable & hot swappable sections, layouts, & animations\n* Strong type checking powered by Swift Generics\n* Reuse everything!\n\nWe think that populating collection view content should be as simple as building custom UIViews. Sections should be reusable and composable into one another. They should define their own layout be easily animatable as well. CollectionKit is our attempt in solving these problems. UICollectionView has been around for 10 years. It is time that we come up with something better **with Swift**.\n\nUnlike traditional UICollectionView's `datasource`/`delegate` methods, CollectionKit uses a single **Provider** object that tells `CollectionView` exactly how to display & handle a collection.\n\nThese Providers are easy to construct, and infinitely composable. Providers also have their own animation and layout objects. You can have sections that layouts and behave differently with in a single `CollectionView`.\n\nCollectionKit already provides many of the commonly used Providers out of the box. But you can still easily create reuseable Provider classes that generalizes on different types on data. Checkout examples down below!", |
| "homepage": "https://github.com/SoySauceLab/CollectionKit", |
| "license": "MIT", |
| "authors": { |
| "Luke": "lzhaoyilun@gmail.com" |
| }, |
| "source": { |
| "git": "https://github.com/SoySauceLab/CollectionKit.git", |
| "tag": "1.3.0" |
| }, |
| "platforms": { |
| "ios": "8.0" |
| }, |
| "ios": { |
| "frameworks": [ |
| "UIKit", |
| "Foundation" |
| ] |
| }, |
| "requires_arc": true, |
| "source_files": "Sources/**/*.swift", |
| "pushed_with_swift_version": "4.0" |
| } |
