Please note: keylime is in the early stages of development and may change. If you develop anything that depends on the current interfaces it would be a good idea to fork. Once things have settled I'll remove this notice.
- Add keylime.xcodeproj to your iOS project (make sure that keylime.xcodeproj is not already opened by XCode).
- Select your current project, then the target you wish to add keylime to, then select the "Build Phases" tab.
- Add keylime to the "Target Dependencies".
- Add libkeylime.a and QuartzCode to "Link Binary With Libraries".
- Select the "Build Settings" tab.
- Add the keylime/src directory to your header search paths.
- If you would like to use keylime's categories add "-all_load" to the "Other Linker Flags".
At this point you should be able to successfully build your project. You can #import "keylime.h", or import the keylime classes independently.
This is where most of keylime's functionality lives. KLViewController offers the ability to provide data for multiple UITableViews. Data can be NSFetchedResultsControllers, Arrays, or any object.
For each individual data object keylime will attempt to find a table view cell named _ClassName_TableViewCell (ie: if keylime sees a 'Person' object it will look for a 'PersonTableViewCell'). If your cell is a derivative of KLTableView cell keylime will automatically call configureWithDataObject: passing the data object.
Base class for table view cells, includes a configureWithDataObject: method that should be overriden to implement your configuration behavior. Make sure to call [super configureWithDataObject: dataObject]; to allow the cell to retain your data object.