Eric, That is too bad. Angular2 was looking really good for us until this snag. This may force us to revisit React, since their component life-cycle model fits very well with a metadata-driven UI. Imagine the *props *of a React component containing the metadata specifying the view. The *render *method would simply code-gen the appropriate virtual DOM tree and render it. A fairly straightforward solution. If the metadata changes, *render *simply re-renders the changes.
If only the Angular2 framework provided better APIs for dynamically creating content. DynamicComponentLoader is not full-featured enough, and is a bit cumbersome to even think about using except in limited cases. Oh well. Thanks for responding. Pete -- 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.
