Sure. How do you make a class a property though? As a string that represents the name of the class? In our case there's still several other things that we want to override though. A lot of it is about the table view formatting, maybe a table view that looks like this should be its own class. Another example is the choice to not render save and cancel buttons. The formCancelled and formSaved delegate methods need to be defined somewhere too. Right now they are in my subclass of the view controller but they have no content. Ideally formSaved will be wired up to a change in a field's value rather than hitting "Save."

here's another question:
In their [demo](https://github.com/frankodwyer/FODFormKit/blob/master/FormKitDemo/FormKitDemo/FODViewController.m), they build the form in some parent view controller and then they initialize fodformviewcontroller with that form. If you run the demo you'll see they have a list of different example forms you can look at, tapping on one brings you into one of the instances of a form. I thought it was a little weird to do the form building outside of the view controller that is used to display the form so I have my form being created in its controller itself. Is one way better than the other? (Not sure if I'm explaining myself very well.)