I don't do this myself, but I think the appeal is being able to define all your models and appropriate UI inputs on the backend, and then expose the same model in multiple views. Then if the model changes, the change only needs to be made in one place on the backend.
On Tuesday, May 20, 2014 7:54:45 AM UTC-4, mark prades wrote: > > The core problem is people addicted to json. AngularJS already provide a >> way to describe components with html and directives.Why would anybody want >> a form generator when one can already describe form controls via directives >> and json ? feels like cargocultiing to me. > > -- 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.
