Skip to content

A lazy way for smart developers to deal with UITableView.

License

Notifications You must be signed in to change notification settings

hieuvo/ATTableView

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

85 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

#ATTableView A lazy way for smart developers to deal with UITableView.

Why ATTableView?

How many times do you have to implement UITableViewDatasource and UITableViewDelegate?
Is it boring? And how to deal with different UITableViewCells in one TableView?

You're smart, so you need a smart way to do it.
ATTableView is for you, it's easy to display model in UITableView. Also support different UITableViewCells.

Traditional way

![alt tag] (/Doc/Assets/OldWay.png)

Your ViewController has to:

  • Implement a lot of methods to adapt UITableViewDatasource and UITableViewDelegate.
  • Do some sucked things like if else condition if you need to display different UITableViewCells in one TableView.
  • Maintain models.
  • Hard to reuse UITableView.

Lazy way

![alt tag] (/Doc/Assets/LazyWay.png)

So now:

  • Don't need to implement any methods of UITableViewDatasource and UITableViewDelegate. Most should be done in UITableViewCell.
  • It's super easy to reuse UITableViewCell.
  • Models are managed by ATTableView, not ViewController anymore.
  • Allow displaying UITableViewCells base on model type without pain. After some setup, just push models to ATTableView, then cell will automatically pick up models and display them.
  • Support Generic and Associated types. So no type casts required.

Introduce ATTableViewCellProtocol

public protocol ATTableViewCellProtocol: NSObjectProtocol {
    typealias ModelType

    // Optional, default is ClassName
    static func reuseIdentifier() -> String

    // Optional, default is ClassName
    static func nibName() -> String?

    // Optional, default is `UITableViewAutomaticDimension`
    static func height(model: ModelType) -> CGFloat

    // Define how to map properties of model to UI.
    // This method must be implemented.
    func configureCell(model: ModelType)
}

ATTableView requires some implementations in your cell, so your cell must implement this protocol.

  • Don't need to implement all, some methods already have default implementation.
  • No type casts required. ModelType is based on your definition.

Sample Project

There's a sample project in the Demo directory. Or follow the instructions [here] (Doc/Examples.md).
Have fun!

Usage

After some setup, using ATTableView is really simple. In your ViewController, just follow these steps below:

1.Register your cells:

self.tableView.register(RestaurantTableViewCell.self)
self.tableView.register(HotelTableViewCell.self)

2.Push your models:

let restaurant = Restaurant()
... // Some extra initializions

let hotel = Hotel()
... // Some extra initializions

self.tableView.addObjects([restaurant, hotel])

3.Enjoy it!

alt tag

Handle click event on Cell

Just easy like this:

self.tableView.onDidSelectItem = { [weak self] item in
    // Handle selected item here
    ...
}

Lazy loading models from Network

Coming soon...

Requirements

  • iOS 8.0+ / Mac OS X 10.9+
  • Xcode 6.4

Installation

CocoaPods is a dependency manager for Cocoa projects.

CocoaPods 0.36 adds supports for Swift and embedded frameworks. You can install it with the following command:

$ gem install cocoapods

To integrate ATTableView into your Xcode project using CocoaPods, specify it in your Podfile:

source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '8.0'
use_frameworks!

pod 'ATTableView', '1.2'

Then, run the following command:

$ pod install

License

ATTableView is released under the MIT license. See LICENSE for details.

About

A lazy way for smart developers to deal with UITableView.

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Swift 79.5%
  • Shell 17.0%
  • Ruby 3.0%
  • Objective-C 0.5%