FRCTableViewDataSources are a more structured way of making an object to use as a data source for a UITableView.
- Automatic handling of table view cells created from nibs or a storyboard
- A fetched results data source that can be fed with a managed object context and fetch request to keep the table view in sync.
- A splitter data source that can be used to join multiple data source objects together
- Data source to represent one object, useful if you want to join a couple of different types of cell representing different objects
- A collapsable data source which provides a header cell, which opens and collapses its children when tapped
iOS 5 and Automatic Reference Counting (ARC)
This project uses ARC, but will work fine with iOS 4.3-style ARC.
It will also work fine when compiled to use iOS 4.3 as the base SDK. When doing so, the new iOS 5 call (
registerNib:forCellReuseIdentifier: on UITableView) is not used. If you use the FRCTableViewDataSource implementation of
tableView:cellForRowAtIndexPath: in data source subclasses, it will yield no ill effect and still give you the nib-based table cell.
This will create a table view with a cell to use as a button to add a timestamp and list all the timestamps below it. This is shown in the MasterViewController in the project in the demo branch.
splitDataSource = [[FRCSplitTableViewDataSource alloc] init]; splitDataSource.type = FRCSplitTableViewDataSourceTypeSection;
addingDataSource = [[FRCObjectTableViewDataSource alloc] init]; addingDataSource.object = @"Add new timestamp"; [splitDataSource addChildTableViewDataSource:addingDataSource];
FRCFetchedResultsTableViewDataSource *fetchedResultsDS = [[FRCFetchedResultsTableViewDataSource alloc] init]; fetchedResultsDS.cellClass = [EventTableViewCell class]; fetchedResultsDS.managedObjectContext = self.managedObjectContext; fetchedResultsDS.fetchRequest = request; // Just some request [splitDataSource addChildTableViewDataSource:fetchedResultsDS];
self.tableView.dataSource = splitDataSource;
There are two branches to this repository, master and demo.
The master branch contains the code and should be used if you want to add these extensions as a git submodule in other projects. It will only contain the class files themselves without the Xcode project or example classes. This is preferable as it will keep your directories clean of any code which is unnecessary to your working project.
To add this project as a submodule you should run the following from inside your project’s git repository:
git submodule add git://github.com/danielctull/FRCTableViewDataSources.git
To keep up to date with the latest changes `cd` into the directory that contains this submodule and pull the newest changes as usual:
git pull origin
This contains an Xcode project that demonstrates the code and is the branch to use to see how to use the code. The demo branch contains a submodule reference to the master branch to bring in the library classes.
To clone the demo branch, while also pulling in any necessary submodules run the following command:
git clone -b demo --recursive git://github.com/danielctull/FRCTableViewDataSources.git
When changing to the demo branch you will need to run through the following set of commands:
git checkout demo git submodule init git submodule update
After these you will see the example project and the library code will be in a sub-directory.
Sometimes, there may be artefacts left over when switching from demo to master. These are files that are ignored by git and are easily cleaned up by running
git clean -dxf
Copyright © 2011 Daniel Tull. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
- Neither the name of the author nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.