I also have a different take on the same sort of idea: https://github.com/saymedia/angularjs-dynamic-form
It's nice that angular-schema-form uses JSON Schema, which angularjs-dynamic-form doesn't... it uses its own minimal schema language. angularjs-dynamic-form has a slightly different design, where HTML elements for a given field type are still provided in the template, and the framework just wraps instances of those in a table based on the provided schema. I thought this represented a good separation of concerns between the view and the model. In our use-case (a system which supports editing of arbitrary data objects based on a schema that can change at runtime) I consider the list of fields to be part of the model, but exactly how those fields are rendered as HTML as a concern for the view. This library could probably integrate better with the existing Angular form/model/validator concepts -- it doesn't really touch that right now -- but we (Say Media) are using it in production right now. I'd also like to add support for generic collection types one day, but I didn't yet find an API design I liked and we haven't yet needed it enough to force the issue. On Tuesday, May 13, 2014 10:29:41 PM UTC-7, Geoffrey Cox wrote: > > Check out https://github.com/Textalk/angular-schema-form > >> >> -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
