Setting minimum deployment target to 5.1, fixed some naming inconsistencies, and created a README.

Author: pwightman

PDTiledView.xcodeproj/project.pbxproj

@@ -407,7 +407,7 @@
 				GCC_PRECOMPILE_PREFIX_HEADER = YES;
 				GCC_PREFIX_HEADER = "PDTiledView/PDTiledView-Prefix.pch";
 				INFOPLIST_FILE = "PDTiledView/PDTiledView-Info.plist";
-				IPHONEOS_DEPLOYMENT_TARGET = ":w";
+				IPHONEOS_DEPLOYMENT_TARGET = 5.1;
 				PRODUCT_NAME = "$(TARGET_NAME)";
 				WRAPPER_EXTENSION = app;
 			};
@@ -419,7 +419,7 @@
 				GCC_PRECOMPILE_PREFIX_HEADER = YES;
 				GCC_PREFIX_HEADER = "PDTiledView/PDTiledView-Prefix.pch";
 				INFOPLIST_FILE = "PDTiledView/PDTiledView-Info.plist";
-				IPHONEOS_DEPLOYMENT_TARGET = ":w";
+				IPHONEOS_DEPLOYMENT_TARGET = 5.1;
 				PRODUCT_NAME = "$(TARGET_NAME)";
 				WRAPPER_EXTENSION = app;
 			};

PDTiledView/PDTiledView/PDTiledView.h

@@ -29,7 +29,7 @@ PDIndexPath PDIndexPathMake(NSInteger section, NSInteger tile) {
 @property (strong, nonatomic) NSInteger (^numberOfSectionsBlock)();
 @property (strong, nonatomic) NSInteger (^numberOfTilesInSectionBlock)(NSInteger section);
 @property (strong, nonatomic) UIControl* (^controlForSectionBlock)(NSInteger section);
-@property (strong, nonatomic) UIControl* (^controlForIndexPathBlock)(PDIndexPath indexPath);
+@property (strong, nonatomic) UIControl* (^controlForTileAtIndexPathBlock)(PDIndexPath indexPath);
 
 #pragma Optional Blocks
 // Default is the width of this PDTiledView, so it will be square

PDTiledView/PDTiledView/PDTiledView.m

@@ -141,7 +141,7 @@ - (void) selectSection:(NSInteger)section animated:(BOOL)animated {
 		tiledScrollView.contentSize = contentSize;
 
 		for (NSInteger i = 0; i < numberOfTiles; i++) {
-			UIControl *control = _controlForIndexPathBlock(PDIndexPathMake(section, i));
+			UIControl *control = _controlForTileAtIndexPathBlock(PDIndexPathMake(section, i));
 
 
 			CGRect frame = CGRectZero;

PDTiledView/PDViewController.m

@@ -44,12 +44,11 @@ - (void)viewDidLoad
 
 	};
 
-	_tiledView.controlForIndexPathBlock = ^UIControl *(PDIndexPath indexPath) {
+	_tiledView.controlForTileAtIndexPathBlock = ^UIControl *(PDIndexPath indexPath) {
 		UIButton *button = [UIButton buttonWithType:UIButtonTypeCustom];
 		button.backgroundColor = [self randomColor];
 		button.layer.borderColor = [[UIColor blackColor] CGColor];
 		button.layer.borderWidth = 1;
-		button.titleLabel.text = [NSString stringWithFormat:@"%@", @(indexPath.tile)];
 		return button;
 	};
 

README.md

@@ -1,4 +1,64 @@
 PDTiledView
 ===========
 
-Accordion-style table view, with block-based delegation.
+Accordion-style table view, with block-based delegation.
+
+## Installation
+
+CocoaPods soon, but you can drop `PDTiledView.h/.m` into your project for now.
+
+## Usage
+
+Very similar to `UITableView`, but uses `sections` and `tiles` instead of `sections` and `rows`. It also uses blocks instead of protocols for delegation.
+
+### Examples
+
+```objective-c
+PDTiledView *tiledView = ...;
+
+tiledView.numberOfSectionsBlock = ^NSInteger{ return 4; };
+
+tiledViewdView.numberOfTilesInSectionBlock = ^NSInteger (NSInteger section) { 
+    return 20; 
+};
+```
+
+All `sections` and `rows` are just UIControl subclasses, such as UIButton or a custom control of your making. (This may switch to UIView later, not sold on it yet).
+
+```objective-c
+tiledView.controlForSectionBlock = ^UIControl *(NSInteger section) {
+    UIButton *button = [UIButton buttonWithType:UIButtonTypeCustom];
+    button.backgroundColor = [UIColor whiteColor];
+    return button;
+};
+
+tiledView.controlForTileAtIndexPathBlock = ^UIControl *(PDTiledViewDIndexPath indexPath) {
+    UIButton *button = [UIButton buttonWithType:UIControlIButtonTypeCustom];
+    return button;
+};
+```
+
+There are also optional blocks to further customize how you like. They match up with their `UITableViewDelegate/DataSource` counterparts:
+
+* `heightForSectionControlBlock`
+* `heightForTilesInSectionBlock`
+* `didSelectSectionBlock`
+* `didSelectTileAtIndexPathBlock`
+* `willDisplaySectionBlock`
+* `willDisplayTileAtIndexPathBlock`
+
+## Discussion
+
+The internal implementation does not use `UITableView`s, so while some things are cached, tiles are not loaded on-the-fly and cached as rows are in UITableView. This shouldn't be a big deal unless you are displaying 1,000s of tiles or tiles are extremely rendering intensive. Pull requests are more than welcome to help implement caching, or perhaps to use `UITableView`s internally.
+
+## Contributing
+
+1. Fork it
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Added some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Create new Pull Request
+
+## Contributors
+
+[Parker Wightman](https://github.com/pwightman) ([@parkerwightman](http://twitter.com/parkerwightman))