Platformsios 6.0, requires ARC


Provides common infrastructure for UITableViews via two UITableViewController subclasses and related support classes.

For form-like table views with a fixed number of rows, such as those found in settings views or those used to edit object data, the you’ll want to subclass RMSFormViewController. For dynamic tables, you’ll want to subclass RMSDynamicTableView.


Using either RMSFormViewController or RMSDynamicViewController frees you from the typical boilerplate code that is often found un UITableViewController subclasses. You’ll end up with cleaner code that is easier to read and maintain.

Refer to "The Form" to learn how to define the structure of an RMSFormViewController table using a plist or JSON. The Table View Demo project includes examples of both dynamic and form-like table views.

Latest podspec

    "name": "RMSTableViews",
    "version": "1.0.9",
    "summary": "Provides support for common UITableViewController usage patterns",
    "description": "RMSTableViewsn===============nnProvides support for common UITableViewController usage patternsnnIntroduces section objects that sits between table views and cells. Base classesnfor common table view controller scenarios remove much of the boiler platenfrom your code. You also get relief from the common if/else structures thatntypically arise in table view delegate/datasource handling.nnRMSTableViews provides extensive support for form-like table views such nas those used for in-app settings and in data-editing views.nn",
    "homepage": "",
    "license": "MIT",
    "authors": {
        "Tony Ingraldi": "[email protected]"
    "platforms": {
        "ios": "6.0"
    "source": {
        "git": "",
        "tag": "1.0.9"
    "source_files": "Source",
    "resources": [
    "requires_arc": true

Pin It on Pinterest

Share This