This looks well designed and useful, but whenever I see a new project like this my first question is "What makes this different?"<p>There are a number of existing form libraries for iOS* that have been around for a while at differing levels of complexity. Could you give a brief summary of why you wrote a new library instead of using one of the existing ones? Putting an explanation like that in the readme would be a great way to explain why you did all this work.<p>*:
<a href="https://github.com/chrismiles/EZForm" rel="nofollow">https://github.com/chrismiles/EZForm</a>
<a href="https://github.com/escoz/QuickDialog" rel="nofollow">https://github.com/escoz/QuickDialog</a>
<a href="https://github.com/ittybittydude/IBAForms" rel="nofollow">https://github.com/ittybittydude/IBAForms</a>
This is cool :) I've actually created something similar for a work-related project, but it's specifically based off Core Data entities and uses QuickDialog for creating and managing the elements (so supporting all the Core Data attribute types is easy, and you get the benefit of the QuickDialog style provider/skinning support). For customisation and validation I use Core Data's user info on properties, which means it's easy to create fully-fledged forms with all attribute types and entity relationship types, predicates, and lots of other little things I've needed with basically zero coding.<p>It's kind of turned into a DSL specified within the Core Data model editor, but with the nature of the project it was for it's saved me a lot of time. I'd love to open-source it if there was interest, but I'd have to look into the logistics :)